Triple
T14801346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rana Sanga of Mewar |
E347916
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Rana Vikramaditya Singh |
E946740
|
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: Rana Vikramaditya Singh | Statement: [Rana Sanga of Mewar, child, Rana Vikramaditya Singh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rana Vikramaditya Singh Context triple: [Rana Sanga of Mewar, child, Rana Vikramaditya Singh]
-
A.
Vikramaditya Singh
chosen
Vikramaditya Singh was a 16th-century ruler of Mewar from the Sisodia Rajput dynasty, known for his turbulent reign marked by internal strife and noble discontent.
-
B.
Randhir
Randhir is an Indian actor, director, and producer best known as a member of the prominent Kapoor film family in Bollywood.
-
C.
Rajiv
Rajiv is an Indian male given name most prominently associated with former Prime Minister Rajiv Gandhi.
-
D.
Rana Kirat Singh
Rana Kirat Singh was the ruler who established the princely state of Dholpur in northern India.
-
E.
Rana Mokal Singh
Rana Mokal Singh was a 15th-century ruler of Mewar in present-day Rajasthan, India, and the father of the renowned Rajput king Rana Kumbha.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe64f6c6148190941b05d06d4dc54d |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:31 a.m.