Triple
T30745306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bábí movement |
E782800
|
entity |
| Predicate | regardedFounderAs |
P110458
|
FINISHED |
| Object | Mahdi |
—
|
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: Mahdi | Statement: [Bábí movement, regardedFounderAs, Mahdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardedFounderAs Context triple: [Bábí movement, regardedFounderAs, Mahdi]
-
A.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
-
B.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
C.
historicalFounderAssociated
chosen
Indicates a relationship where an entity is connected to a historical founder, such as being established, inspired, or originally led by that founder.
-
D.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
E.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
- 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_69f68f6cba0c8190a02288899be05007 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.