Triple
T6986267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centzon Huitznahua |
E161969
|
entity |
| Predicate | worldviewContext |
P2919
|
FINISHED |
| Object | Mexica cosmology |
—
|
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: Mexica cosmology | Statement: [Centzon Huitznahua, worldviewContext, Mexica cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldviewContext Context triple: [Centzon Huitznahua, worldviewContext, Mexica cosmology]
-
A.
worldview
Indicates the overarching perspective or framework through which an entity interprets and understands the world and its experiences.
-
B.
worldDefinitionInContext
Indicates that a particular definition of a term or concept is specified as it applies within a given context or situation.
-
C.
worldStyle
Indicates the stylistic or aesthetic manner in which a world, setting, or environment is presented or designed.
-
D.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
E.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.