Triple
T32924821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | definesEpochFor |
P29497
|
FINISHED |
| Object | Baháʼí liturgical 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áʼí liturgical calendar | Statement: [Baháʼí Era, definesEpochFor, Baháʼí liturgical calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEpochFor Context triple: [Baháʼí Era, definesEpochFor, Baháʼí liturgical calendar]
-
A.
associatedEpoch
Indicates a relationship where something is linked to, or occurs within, a particular historical or temporal epoch.
-
B.
mappingEpoch
Indicates the specific time period or version during which a particular mapping or correspondence between entities is defined or valid.
-
C.
DecEpoch
Indicates the specific point in time (epoch) at which a declination (Dec) measurement or coordinate value is defined or referenced.
-
D.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
E.
isEpochBoundaryFor
chosen
Indicates that something marks or defines the transition point between two distinct epochs for another entity.
- 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_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 1:20 a.m.