Triple
T14565950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chol Maya |
E341784
|
entity |
| Predicate | usesCalendarElements |
P1818
|
FINISHED |
| Object | Maya ritual calendar (in syncretic forms) |
—
|
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: Maya ritual calendar (in syncretic forms) | Statement: [Chol Maya, usesCalendarElements, Maya ritual calendar (in syncretic forms)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCalendarElements Context triple: [Chol Maya, usesCalendarElements, Maya ritual calendar (in syncretic forms)]
-
A.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
C.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
-
D.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
-
E.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38c6350819091090ffd15772f6f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.