Triple
T32924803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | definesYearCountFor |
P6440
|
FINISHED |
| Object | Baháʼí calendar |
—
|
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: Baháʼí calendar | Statement: [Baháʼí Era, definesYearCountFor, Baháʼí calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesYearCountFor Context triple: [Baháʼí Era, definesYearCountFor, Baháʼí calendar]
-
A.
specifiedYear
Indicates that a particular year has been explicitly designated or identified in relation to the subject.
-
B.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
countsYearsFrom
chosen
Indicates a temporal relationship where the number of years is measured starting from a specified reference point or event.
-
D.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
E.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
- 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_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:20 a.m.