Triple
T16609271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsi cemetery, Ootacamund (Ooty) |
E403523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Zoroastrian cemetery |
C14638
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Zoroastrian cemetery Context triple: [Parsi cemetery, Ootacamund (Ooty), instanceOf, Zoroastrian cemetery]
-
A.
Zoroastrian funerary structure
chosen
A Zoroastrian funerary structure is a sacred architectural space, such as a tower of silence or charnel house, designed according to religious purity laws to expose or contain the dead without contaminating earth, fire, or water.
-
B.
Phoenician necropolis
A Phoenician necropolis is a burial complex or cemetery used by the ancient Phoenician civilization, typically featuring rock-cut tombs, sarcophagi, and grave goods that reflect their funerary practices and beliefs about the afterlife.
-
C.
Calvary
Calvary is a conceptual class representing the site and event of Jesus Christ’s crucifixion, encompassing its physical location, historical context, and theological significance within Christian tradition.
-
D.
Nabataean tomb
A Nabataean tomb is a rock-cut or freestanding funerary monument, typically carved into sandstone cliffs and characterized by a blend of local, Hellenistic, and Near Eastern architectural elements, used by the Nabataean civilization to bury and honor their dead.
-
E.
funerary garden
A funerary garden is a specially designed outdoor space that commemorates the dead through symbolic plantings, memorial structures, and contemplative areas for mourning and remembrance.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.