Triple
T23883891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Round |
E600278
|
entity |
| Predicate | cycleLengthWhenCombined |
P27022
|
FINISHED |
| Object | 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: 52 Haabʼ years | Statement: [Sacred Round, cycleLengthWhenCombined, 52 Haabʼ years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleLengthWhenCombined Context triple: [Sacred Round, cycleLengthWhenCombined, 52 Haabʼ years]
-
A.
hasCycleLength
chosen
Indicates that an entity participates in or exhibits a cycle whose duration or size is specified by the associated length value.
-
B.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
C.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
D.
typicalNumberOfCycles
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
-
E.
pairedCycle
Indicates a relationship where two cycles are associated or matched together as corresponding counterparts.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ccfbbe4c819093e590709719ab72 |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.