Triple
T3848226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Haryana |
E85224
|
entity |
| Predicate | officeHoldersInclude |
P537
|
FINISHED |
| Object | Bhim Singh |
E394090
|
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: Bhim Singh | Statement: [Governor of Haryana, officeHoldersInclude, Bhim Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhim Singh Context triple: [Governor of Haryana, officeHoldersInclude, Bhim Singh]
-
A.
Beant Singh
Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
-
B.
Maha Singh
Maha Singh was a prominent Sikh chieftain of the Sukerchakia Misl and an important leader in late 18th-century Punjab, best known as the father of Maharaja Ranjit Singh.
-
C.
Man Singh
Man Singh was an Indian noble and close associate of Nana Sahib who played a role in the events of the 1857 Indian Rebellion.
-
D.
Mahal Singh Bhatti
chosen
Mahal Singh Bhatti is an Indian politician who has served as the Governor of the state of Haryana.
-
E.
Lal Singh
Lal Singh was a prominent Sikh military leader and political figure who played a key command role during the Anglo-Sikh Wars in the mid-19th century.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcc8a0481909c35161336bdfbf9 |
completed | March 9, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5122eb2708190b1aa9da233481015 |
completed | March 14, 2026, 7:45 a.m. |
Created at: March 9, 2026, 3:19 p.m.