Triple
T32924813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | predecessorEraInRegion |
P182415
|
FINISHED |
| Object | Islamic Hijri era |
—
|
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: Islamic Hijri era | Statement: [Baháʼí Era, predecessorEraInRegion, Islamic Hijri era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraInRegion Context triple: [Baháʼí Era, predecessorEraInRegion, Islamic Hijri era]
-
A.
predecessorAutonomousRegion
Indicates that one autonomous region previously existed in place of, or was succeeded by, another autonomous region in an administrative or historical sequence.
-
B.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
C.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
D.
precedesEraName
chosen
Indicates that one era occurs entirely before another era in chronological order.
-
E.
predecessorArea
Indicates that one area previously existed or was defined before another area in a sequence or versioning of areas.
- 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_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:20 a.m.