Triple
T19670059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raja Bhoj |
E472309
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Bhoja |
—
|
NE NERFINISHED |
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: Bhoja | Statement: [Raja Bhoj, name, Bhoja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhoja Context triple: [Raja Bhoj, name, Bhoja]
-
A.
Bhoja
Bhoja refers to an ancient Indian clan or dynasty traditionally associated with the Yadava lineage and mentioned in various historical and epic sources.
-
B.
Bhoja
chosen
Bhoja was a renowned 11th-century king and polymath of the Paramara dynasty, celebrated for his military prowess, patronage of arts and literature, and extensive scholarly works.
-
C.
Bhojraj
Bhojraj was a historical figure from the Bundelkhand region of India, known primarily as a member of the royal lineage associated with the famed ruler Chhatrasal.
-
D.
Bhoj Raj
Bhoj Raj was a Rajput prince of Mewar, best known as the first husband of the famed Hindu mystic poet-saint Meera Bai.
-
E.
Durlabharaja
Durlabharaja was a medieval Indian ruler, likely a Chaulukya (Solanki) prince or king of Gujarat, known from inscriptions and genealogies of the dynasty.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416b9cf8819096f44e3f9fbf86fa |
completed | April 20, 2026, 3:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.