Triple
T23883889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Round |
E600278
|
entity |
| Predicate | formsCalendarRoundWith |
P153932
|
FINISHED |
| Object | Haabʼ |
—
|
NE NERFINISHED |
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: Haabʼ | Statement: [Sacred Round, formsCalendarRoundWith, Haabʼ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsCalendarRoundWith Context triple: [Sacred Round, formsCalendarRoundWith, Haabʼ]
-
A.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
B.
calendarContribution
Indicates a relationship where an entity adds to, modifies, or otherwise participates in the creation or maintenance of a calendar or scheduled events.
-
C.
calendarFunction
Indicates a relationship where an entity serves as a function or operation within a calendar system, such as computing or manipulating dates, times, or calendar-related events.
-
D.
calendarAssociation
Indicates a relationship where one entity is linked to or associated with a particular calendar or calendaring context (such as events, schedules, or timeframes).
-
E.
calendarLinkedTo
Indicates that one calendar is connected or synchronized with another calendar or calendaring system so that events or updates can be shared or reflected between them.
- 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_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. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:24 p.m.