Triple
T6561320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calendar Round |
E153787
|
entity |
| Predicate | hasEraReset |
P71816
|
FINISHED |
| Object | every 52 Haab' 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: every 52 Haab' years | Statement: [Calendar Round, hasEraReset, every 52 Haab' years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraReset Context triple: [Calendar Round, hasEraReset, every 52 Haab' years]
-
A.
preservesEra
Indicates that something maintains or keeps intact the characteristics, style, or conditions of a particular historical period.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
D.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
E.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6c1b007148190b5164d6d09584cdf |
completed | March 27, 2026, 5:43 p.m. |
Created at: March 27, 2026, 1:52 p.m.