Triple
T4656967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagat Singh |
E102432
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Jagat Singh |
E102432
|
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: Jagat Singh | Statement: [Jagat Singh, name, Jagat Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jagat Singh Context triple: [Jagat Singh, name, Jagat Singh]
-
A.
Jagat Singh
chosen
Jagat Singh was a brother of Indian revolutionary Bhagat Singh, belonging to the same politically active Sandhu Jat Sikh family from Punjab.
-
B.
Beant Singh
Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
-
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.
Anant Singh
Anant Singh is a prominent South African film producer of Indian origin, best known for producing critically acclaimed anti-apartheid and socially conscious films.
-
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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd631a855c81909773737fd238a14d |
completed | March 20, 2026, 3:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be0378825881908fe3214f60be579e |
completed | March 21, 2026, 2:33 a.m. |
Created at: March 20, 2026, 1:14 p.m.