Triple
T36948528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec calendar |
E913985
|
entity |
| Predicate | hasRitualCalendarStructure |
P31654
|
FINISHED |
| Object | 20 day signs and 13 numbers |
—
|
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: 20 day signs and 13 numbers | Statement: [Aztec calendar, hasRitualCalendarStructure, 20 day signs and 13 numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualCalendarStructure Context triple: [Aztec calendar, hasRitualCalendarStructure, 20 day signs and 13 numbers]
-
A.
hasRitualCalendar
chosen
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
B.
hasRitualCalendarLength
Indicates the relationship between an entity and the specific duration or length of its ritual calendar.
-
C.
hasRitualCalendarName
Indicates that an entity is associated with a specific name used for it in a ritual or ceremonial calendar.
-
D.
hasRitualDay
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
-
E.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:13 p.m.