Triple

T36929933
Position Surface form Disambiguated ID Type / Status
Subject Xiuhpohualli E913449 entity
Predicate hasCycleLengthWithTonalpohualli P157629 FINISHED
Object 52 years 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: 52 years | Statement: [Xiuhpohualli, hasCycleLengthWithTonalpohualli, 52 years]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCycleLengthWithTonalpohualli
Context triple: [Xiuhpohualli, hasCycleLengthWithTonalpohualli, 52 years]
  • A. cycleLengthWithTonalpohualli chosen
    Indicates the length of a recurring cycle as it aligns or synchronizes with the Tonalpohualli (the Mesoamerican 260-day ritual calendar).
  • B. hasCycleLength
    Indicates that an entity participates in or exhibits a cycle whose duration or size is specified by the associated length value.
  • C. heavenlyStemsCycleLength
    Indicates the length of the repeating cycle of the Heavenly Stems sequence in a calendrical or ordinal system.
  • D. hasNumberInCycle
    Indicates that a given number appears within a specified repeating sequence or cycle associated with an entity or process.
  • E. hasRitualCalendarLength
    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_69f76e896c988190880c130e01303dd4 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fa0a7b00948190a257273d9968c5d7 completed May 5, 2026, 3:19 p.m.
PD Predicate disambiguation batch_69f9fec9c9488190ae2a349651a02782 completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:13 p.m.