Triple
T31306764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bábís |
E798352
|
entity |
| Predicate | historicalSuccessorMovement |
P95379
|
FINISHED |
| Object | Baháʼís |
E42142
|
NE 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: Baháʼís | Statement: [Bábís, historicalSuccessorMovement, Baháʼís]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuccessorMovement Context triple: [Bábís, historicalSuccessorMovement, Baháʼís]
-
A.
historicalSuccessorState
Indicates that one state historically followed and replaced another state in time as its successor.
-
B.
historicalSuccessorInNationStateContext
Indicates that one political entity directly follows another as its successor within the historical continuity of a nation-state.
-
C.
successorInMovement
chosen
Indicates that one movement directly follows another in a sequence or progression.
-
D.
historicalMovementAssociatedWith
Indicates that there is an association between an entity and a historical movement, such as a social, political, cultural, or ideological current in history.
-
E.
formerMovement
Indicates that an entity previously belonged to or was associated with a particular movement but is no longer part of it.
- F. None of above.
Provenance (4 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370d9e17a88190883cdcefbd86c2a6 |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 29, 2026, 9:14 p.m.