Triple
T32924756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayyám-i-Há |
E842235
|
entity |
| Predicate | purposeInCalendar |
P156313
|
FINISHED |
| Object | to adjust solar year in Badí‘ calendar |
—
|
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: to adjust solar year in Badí‘ calendar | Statement: [Ayyám-i-Há, purposeInCalendar, to adjust solar year in Badí‘ calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeInCalendar Context triple: [Ayyám-i-Há, purposeInCalendar, to adjust solar year in Badí‘ calendar]
-
A.
calendarUsedFor
chosen
Indicates that a particular calendar is employed or applied for a specific purpose, context, or activity.
-
B.
importanceInCalendar
Indicates the relative priority or significance assigned to an event or item within a calendar.
-
C.
roleInCalendar
Indicates that an entity holds a specific role or function within the context of a particular calendar or scheduled event.
-
D.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
E.
calendarContribution
Indicates a relationship where an entity adds to, modifies, or otherwise participates in the creation or maintenance of a calendar or scheduled events.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0d980208190b9038470f1e4022e |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.