Triple
T34785732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babi movement in Iran |
E1002798
|
entity |
| Predicate | notableFemaleFigure |
P82686
|
FINISHED |
| Object | Táhirih |
E1928657
|
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: Táhirih | Statement: [Babi movement in Iran, notableFemaleFigure, Táhirih]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFemaleFigure Context triple: [Babi movement in Iran, notableFemaleFigure, Táhirih]
-
A.
notableFemaleMember
chosen
Indicates that an entity has a female member who is particularly prominent, distinguished, or noteworthy within that entity.
-
B.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
C.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
D.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fa2293c8190b04aca526341a45d |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.