Triple
T6561305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calendar Round |
E153787
|
entity |
| Predicate | notationIncludes |
P42643
|
FINISHED |
| Object | Tzolk'in day name |
—
|
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: Tzolk'in day name | Statement: [Calendar Round, notationIncludes, Tzolk'in day name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notationIncludes Context triple: [Calendar Round, notationIncludes, Tzolk'in day name]
-
A.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
notationDomain
chosen
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
C.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
- 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.