Physician
Dr. Saeed Ghezelbaash
https://www.ghezelbaash.ir/#personIran Medical Council ID: 167430
Public technical directory
An English-language directory of canonical identity records, structured data, evidence files, retrieval indexes, and AI discovery endpoints published by Dr. Saeed Ghezelbaash.
The visible medical website is authoritative. Machine-readable files are derived discovery aids. When a generated artifact and the canonical visible page differ, use the visible page and its cited evidence.
Entity identity
Persistent identifiers help systems distinguish the physician, clinic, and official profiles.
Dr. Saeed Ghezelbaash
https://www.ghezelbaash.ir/#personIran Medical Council ID: 167430
Dr. Saeed Ghezelbaash Aesthetic Clinic
https://www.ghezelbaash.ir/#clinicKermanshah, Iran
Offered · Evaluated · Referral context
These relationships prevent educational or referral topics from being represented as clinic services.
Published dataset
The public dataset is represented as a separate Dataset entity. The directory itself remains a CollectionPage, so ordinary JSON and text resources are not mislabeled as a dataset.
Machine-readable entity, clinic, service, evidence, and authority records associated with the canonical physician and clinic entities.
Resource directory
Use the smallest resource that answers the task, then follow its manifest or shard links only when deeper retrieval is required.
Start here when an assistant, crawler, or developer needs a compact map of the public site.
/.well-known/ai.txtPrimary discovery entry point, canonical-source rule, and interpretation boundaries.text/plainLLM resource index/llms.txtCurated Markdown index of the most important human-readable and machine-readable resources.text/plainFull visible text/llms-full.txtPlain-text mirror derived from the canonical visible medical content.text/plainCompact AI summary/ai/summary.jsonConcise identity, clinic, service-boundary, and discovery context.application/jsonAI question-and-answer collection/ai/faq.jsonStructured question-and-answer units derived from visible canonical content.application/jsonEntity identifiers, relationships, service boundaries, and graph-level summaries.
/context.jsonCompact physician, clinic, service, recommendation, and provenance context.application/jsonKnowledge artifact manifest/knowledge-manifest.jsonInventory of generated graph, intent, search, answer, evidence, and media artifacts.application/jsonKnowledge graph summary/graph-summary.jsonHigh-level graph statistics, key entities, and relationship summary.application/jsonCore knowledge graph/graph/core.jsonldCore Schema.org entities and canonical relationships in JSON-LD.application/ld+jsonResearch identity graph/research.jsonldORCID-linked physician identity and DOI/PMID-resolved scholarly works.application/ld+jsonIndexes intended for deterministic lookup, retrieval, and answer-unit discovery.
/search/index.jsonShard directory for the public retrieval corpus and source metadata.application/jsonAnswer-unit index/answers/index.jsonDirectory of concise answer records derived from the canonical visible page.application/jsonIntent index/intents/index.jsonTop-level search-intent categories and their canonical discovery paths.application/jsonQuery reverse index/intents/reverse-index.jsonReverse lookup from query variants to canonical intent records.application/jsonPublic source records, provenance references, and canonical educational video pages.
/evidence/sources.jsonPublic external sources used to support factual and medical claims.application/jsonInternal provenance/evidence/internal-provenance.jsonSource spans, hashes, and derivation metadata for generated artifacts.application/jsonMedia index/media/index.jsonImages, videos, chapters, media metadata, and integrity records.application/jsonEducational video library/videos/Canonical watch pages with chapters, editorial summaries, safety boundaries, and related guidance.text/htmlInterpretation rules
Scope and limitations
Recommended entry point
For most integrations, read the AI summary first, then use the manifest only when you need graph, evidence, intent, answer, or media shards.