Triple
T10113458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridván |
E218297
|
entity |
| Predicate | endDateInBahá'íCalendar |
P87799
|
FINISHED |
| Object | 14th day of Jalál |
—
|
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: 14th day of Jalál | Statement: [Ridván, endDateInBahá'íCalendar, 14th day of Jalál]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateInBahá'íCalendar Context triple: [Ridván, endDateInBahá'íCalendar, 14th day of Jalál]
-
A.
endDateInRepublicanCalendar
Indicates that the end date of an event or interval is expressed using the French Republican calendar system.
-
B.
dayInBadíCalendar
chosen
Indicates that a given day corresponds to a specific day position within the Badí (Bahá’í) calendar system.
-
C.
dateInHebrewCalendar
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.