Triple
T36929884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiuhmolpilli |
E913448
|
entity |
| Predicate | timeReckoningRole |
P97348
|
FINISHED |
| Object | major period in Aztec chronology |
—
|
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: major period in Aztec chronology | Statement: [Xiuhmolpilli, timeReckoningRole, major period in Aztec chronology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeReckoningRole Context triple: [Xiuhmolpilli, timeReckoningRole, major period in Aztec chronology]
-
A.
timeCycleRole
chosen
Indicates a role or function that an entity plays within a recurring or cyclical time pattern (such as a specific position or duty in a repeated time cycle).
-
B.
screenTimeRole
Indicates the role or capacity in which an entity appears on screen, such as main, supporting, cameo, or other participation type.
-
C.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
D.
roleAtA24
Indicates that an entity holds or held a specific role or position at the organization or project referred to as A24.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.