Triple
T14491203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhima I |
E359365
|
entity |
| Predicate | title |
P38
|
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: [Bhima I, title, Maharajadhiraja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maharajadhiraja Context triple: [Bhima I, title, Maharajadhiraja]
-
A.
Rajarshi
Rajarshi is an honorific title in ancient Indian tradition denoting a king who has attained the spiritual wisdom and detachment of a sage.
-
B.
Samraj Jaimungal
Samraj Jaimungal is a Trinidadian chutney-soca singer and entertainer better known by his stage name Rikki Jai.
-
C.
Maharaja Rana
Maharaja Rana was the hereditary royal title borne by the sovereign rulers of the princely state of Porbandar in pre-independence India.
-
D.
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.
-
E.
Raja
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d9334708190baa2f8094df3c09e |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:20 a.m.