Triple
T15704378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranjitsinhji |
E380668
|
entity |
| Predicate | monarchPredecessor |
P24974
|
FINISHED |
| Object |
Jaswantsinhji
Jaswantsinhji was an Indian princely ruler who reigned over Nawanagar before his successor, the famed cricketer-king Ranjitsinhji.
|
E1172138
|
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: Jaswantsinhji | Statement: [Ranjitsinhji, monarchPredecessor, Jaswantsinhji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaswantsinhji Context triple: [Ranjitsinhji, monarchPredecessor, Jaswantsinhji]
-
A.
Gobind
Gobind is the given name of Guru Gobind Singh, the tenth Sikh Guru and a central figure in Sikh history.
-
B.
Jagat Singh
Jagat Singh was a brother of Indian revolutionary Bhagat Singh, belonging to the same politically active Sandhu Jat Sikh family from Punjab.
-
C.
Jagat Singh
Jagat Singh was a ruler from the Mewar dynasty in Rajasthan, India, after whom the historic island palace Jag Mandir in Udaipur is named.
-
D.
Jagat Singh
Jagat Singh is a central fictional nobleman and romantic hero in Bankim Chandra Chattopadhyay’s historical novel "Durgeshnandini."
-
E.
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.
- 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: Jaswantsinhji Triple: [Ranjitsinhji, monarchPredecessor, Jaswantsinhji]
Generated description
Jaswantsinhji was an Indian princely ruler who reigned over Nawanagar before his successor, the famed cricketer-king Ranjitsinhji.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Jaswantsinhji Target entity description: Jaswantsinhji was an Indian princely ruler who reigned over Nawanagar before his successor, the famed cricketer-king Ranjitsinhji.
-
A.
Gobind
Gobind is the given name of Guru Gobind Singh, the tenth Sikh Guru and a central figure in Sikh history.
-
B.
Jagat Singh
Jagat Singh was a brother of Indian revolutionary Bhagat Singh, belonging to the same politically active Sandhu Jat Sikh family from Punjab.
-
C.
Jagat Singh
Jagat Singh is a central fictional nobleman and romantic hero in Bankim Chandra Chattopadhyay’s historical novel "Durgeshnandini."
-
D.
Jagat Singh
Jagat Singh was a ruler from the Mewar dynasty in Rajasthan, India, after whom the historic island palace Jag Mandir in Udaipur is named.
-
E.
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.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f6fc3608190a85b25755f5345db |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff757997348190b29a9b55ba08169f |
completed | May 9, 2026, 5:57 p.m. |
| NEDg | Description generation | batch_69ff7653ccc08190b4b44b4f55344f65 |
completed | May 9, 2026, 6 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff76d21a148190bbe66c3ff12386f3 |
completed | May 9, 2026, 6:02 p.m. |
Created at: April 10, 2026, 4:45 a.m.