Triple
T27496135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taj Khan Karrani |
E694022
|
entity |
| Predicate | successorStateToDynastyFounded |
P187370
|
FINISHED |
| Object | Mughal Bengal |
—
|
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: Mughal Bengal | Statement: [Taj Khan Karrani, successorStateToDynastyFounded, Mughal Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStateToDynastyFounded Context triple: [Taj Khan Karrani, successorStateToDynastyFounded, Mughal Bengal]
-
A.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
B.
branchOfDynastyFounded
Indicates that one dynasty is a branch or offshoot of another, earlier-founded dynasty.
-
C.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
D.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
-
E.
dynastyFoundedByOffspring
Indicates that a dynasty was established by the offspring (child or descendant) of a particular person or entity.
- F. None of above. chosen
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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 27, 2026, 1:08 p.m.