Triple
T30745314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bábí movement |
E782800
|
entity |
| Predicate | hasNotableDisciple |
P38326
|
FINISHED |
| Object | Subh-i-Azal |
—
|
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: Subh-i-Azal | Statement: [Bábí movement, hasNotableDisciple, Subh-i-Azal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDisciple Context triple: [Bábí movement, hasNotableDisciple, Subh-i-Azal]
-
A.
wasDiscipleOf
chosen
Indicates that one entity served as a disciple, student, or follower under the guidance or teaching of another entity.
-
B.
hasDisciplesAndFollowersTradition
Indicates that an entity has an associated tradition concerning its disciples and followers, including how they are understood, organized, or transmitted over time.
-
C.
hasNotableClergyman
Indicates that an entity is associated with a clergyman who is distinguished or notable in some recognized way.
-
D.
disciplesType
Indicates the specific category or kind of discipleship relationship that exists between the involved entities.
-
E.
hasApostle
Indicates that a person or deity is associated with, or has, one or more apostles devoted to following or spreading their teachings.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: April 29, 2026, 8:38 p.m.