Triple
T32924794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | startDateGregorian |
P16736
|
FINISHED |
| Object | 23 May 1844 |
—
|
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: 23 May 1844 | Statement: [Baháʼí Era, startDateGregorian, 23 May 1844]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateGregorian Context triple: [Baháʼí Era, startDateGregorian, 23 May 1844]
-
A.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
-
B.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
-
C.
calendarEpoch
chosen
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 1, 2026, 1:20 a.m.