Triple
T9031564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandela dynasty |
E216383
|
entity |
| Predicate | dynasticTitle |
P593
|
FINISHED |
| Object | Maharajadhiraja |
E92074
|
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: Maharajadhiraja | Statement: [Chandela dynasty, dynasticTitle, Maharajadhiraja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maharajadhiraja Context triple: [Chandela dynasty, dynasticTitle, Maharajadhiraja]
-
A.
Maharaja Rana
Maharaja Rana was the hereditary royal title borne by the sovereign rulers of the princely state of Porbandar in pre-independence India.
-
B.
Maharaja
chosen
Maharaja is a royal title historically used by sovereign Hindu and Sikh rulers in the Indian subcontinent, denoting a "great king" or high-ranking monarch.
-
C.
Raja
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
-
D.
Maharana
Maharana is a hereditary royal title used by the rulers of certain princely states in India, notably the Sisodia dynasty of Mewar based in Udaipur.
-
E.
Hirak Raja
Hirak Raja is the tyrannical diamond-obsessed king in Satyajit Ray’s Bengali fantasy film "Hirak Rajar Deshe."
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6a9f2c7481909b4a272183f20585 |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb83e8988190bf29baa1aff11ac0 |
completed | April 3, 2026, 4:32 p.m. |
Created at: March 30, 2026, 7:08 p.m.