Triple
T6239998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durgeshnandini |
E139574
|
entity |
| Predicate | hasMainCharacter |
P1183
|
FINISHED |
| Object |
Jagat Singh
Jagat Singh is a central fictional nobleman and romantic hero in Bankim Chandra Chattopadhyay’s historical novel "Durgeshnandini."
|
E585556
|
NE FINISHED |
How this triple was built (4 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: [Durgeshnandini, hasMainCharacter, Jagat Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jagat Singh Context triple: [Durgeshnandini, hasMainCharacter, Jagat Singh]
-
A.
Jagat Singh
Jagat Singh was a brother of Indian revolutionary Bhagat Singh, belonging to the same politically active Sandhu Jat Sikh family from Punjab.
-
B.
Jagdanand Singh
Jagdanand Singh is an Indian politician and senior leader of the Rashtriya Janata Dal, known for his long-standing role in Bihar state politics.
-
C.
Jhujhar Singh
Jhujhar Singh was a 17th-century Bundela Rajput ruler of Orchha in central India, known for his conflicts with the Mughal Empire during Shah Jahan’s reign.
-
D.
Beant Singh
Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Jagat Singh Triple: [Durgeshnandini, hasMainCharacter, Jagat Singh]
Generated description
Jagat Singh is a central fictional nobleman and romantic hero in Bankim Chandra Chattopadhyay’s historical novel "Durgeshnandini."
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Jagat Singh Target entity description: Jagat Singh is a central fictional nobleman and romantic hero in Bankim Chandra Chattopadhyay’s historical novel "Durgeshnandini."
-
A.
Jagat Singh
Jagat Singh was a brother of Indian revolutionary Bhagat Singh, belonging to the same politically active Sandhu Jat Sikh family from Punjab.
-
B.
Jagdanand Singh
Jagdanand Singh is an Indian politician and senior leader of the Rashtriya Janata Dal, known for his long-standing role in Bihar state politics.
-
C.
Jhujhar Singh
Jhujhar Singh was a 17th-century Bundela Rajput ruler of Orchha in central India, known for his conflicts with the Mughal Empire during Shah Jahan’s reign.
-
D.
Beant Singh
Beant Singh was one of the Sikh bodyguards who assassinated Indian Prime Minister Indira Gandhi in 1984.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063067d9c819085a18d9d03939266 |
completed | March 22, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c603ea4b64819098abfe83fc5003aa |
completed | March 27, 2026, 4:13 a.m. |
| NEDg | Description generation | batch_69c60506f7d0819084d5a757cdf395a1 |
completed | March 27, 2026, 4:18 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c605d48e848190bf11f3862a12d709 |
completed | March 27, 2026, 4:21 a.m. |
Created at: March 22, 2026, 4:23 p.m.