Triple
T16725329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicomoztoc |
E406450
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary place of origin |
C5600
|
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: legendary place of origin Context triple: [Chicomoztoc, instanceOf, legendary place of origin]
-
A.
mythological place
chosen
A mythological place is an imagined or legendary location rooted in cultural myths, folklore, or religious narratives, often embodying symbolic meanings, supernatural qualities, or moral themes rather than a verifiable physical existence.
-
B.
legendary city
A legendary city is a mythical or semi-mythical urban center, often described in folklore or ancient texts, renowned for its extraordinary wealth, advanced culture, or mysterious disappearance.
-
C.
mythological location
A mythological location is an imagined place rooted in folklore, religion, or legend, often imbued with supernatural qualities and symbolic meaning within a culture’s narrative tradition.
-
D.
ancestral homeland
An ancestral homeland is a geographic region to which a person or group traces deep historical, cultural, or familial origins, often forming a core part of their collective identity.
-
E.
ancient place
An ancient place is a historically significant location from antiquity, often associated with early civilizations, archaeological remains, or long-standing cultural traditions.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.