Triple
T7608119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coatepec |
E180159
|
entity |
| Predicate | hasPrimaryMyth |
P9998
|
FINISHED |
| Object | birth of Huitzilopochtli from Coatlicue |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: birth of Huitzilopochtli from Coatlicue | Statement: [Coatepec, hasPrimaryMyth, birth of Huitzilopochtli from Coatlicue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryMyth Context triple: [Coatepec, hasPrimaryMyth, birth of Huitzilopochtli from Coatlicue]
-
A.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
B.
hasMythType
chosen
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
C.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
-
D.
hasMythologicalFamily
Indicates that an entity is related to another entity as part of its mythological family or lineage (e.g., gods, heroes, or legendary ancestors).
-
E.
hasMythologicalOpponents
Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
- F. None of above.
Provenance (3 batches)
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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1de8a4819091f9e9347835ce16 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.