Triple
T1418110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Jafar |
E31964
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Miran |
E162672
|
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: Miran | Statement: [Mir Jafar, successor, Miran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miran Context triple: [Mir Jafar, successor, Miran]
-
A.
Miran
chosen
Miran was the son of Mir Jafar, the controversial Nawab of Bengal installed by the British East India Company in the mid-18th century.
-
B.
Mella
Mella is a Spanish-language surname most notably associated with Cuban revolutionary leader Julio Antonio Mella.
-
C.
Micali
Micali is an Italian surname most notably associated with Silvio Micali, a Turing Award–winning computer scientist and cryptographer.
-
D.
Mila
Mila is a leading artificial intelligence research institute based in Quebec, renowned for its work in deep learning and machine learning.
-
E.
Mara
Mara is a surname of Irish origin borne by various notable individuals in fields such as sports, entertainment, and politics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c404e92c8190bd018673383f4534 |
completed | March 1, 2026, 10:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad015cdc8881908887aa0fb0838145 |
completed | March 8, 2026, 4:55 a.m. |
Created at: March 1, 2026, 7:59 p.m.