Triple
T11241888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya calendar |
E266090
|
entity |
| Predicate | TzolkʼinLength |
P71811
|
FINISHED |
| Object | 260 days |
—
|
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: 260 days | Statement: [Maya calendar, TzolkʼinLength, 260 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TzolkʼinLength Context triple: [Maya calendar, TzolkʼinLength, 260 days]
-
A.
heavenlyStemsCycleLength
Indicates the length of the repeating cycle of the Heavenly Stems sequence in a calendrical or ordinal system.
-
B.
zodiacCycleLength
Indicates the duration or number of units that a complete zodiac cycle takes to repeat.
-
C.
timeInAztecYear
Indicates that a specific time or date occurs within a particular year as defined by the Aztec calendar system.
-
D.
earthlyBranchesCycleLength
Indicates the length of the repeating cycle formed by the sequence of earthly branches in a given calendrical or symbolic system.
-
E.
hasRitualCalendarLength
chosen
Indicates the relationship between an entity and the specific duration or length of its ritual calendar.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e919eaf48190a1457851cfc56afb |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.