Triple
T6561118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzolkʼin calendar |
E153783
|
entity |
| Predicate | hasNumberRange |
P15776
|
FINISHED |
| Object | 1 to 13 |
—
|
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: 1 to 13 | Statement: [Tzolkʼin calendar, hasNumberRange, 1 to 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberRange Context triple: [Tzolkʼin calendar, hasNumberRange, 1 to 13]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasDayNumberRange
chosen
Indicates that something is associated with a contiguous range of day numbers between a specified minimum and maximum value.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
-
E.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.