Triple
T5505508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindusara |
E144428
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Samrat |
E310655
|
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: Samrat | Statement: [Bindusara, title, Samrat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samrat Context triple: [Bindusara, title, Samrat]
-
A.
Raja Dahir
Raja Dahir was the last Hindu ruler of Sindh, known for his defeat and death in 712 CE during the Arab conquest of the region led by Muhammad bin Qasim.
-
B.
Akrura
Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
-
C.
Rajasanagara
Rajasanagara is the regnal name of Hayam Wuruk, the 14th-century king under whom the Majapahit Empire in Java reached its peak of power and cultural influence.
-
D.
Raja
chosen
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
-
E.
Rajasuya
Rajasuya is an ancient Vedic royal consecration ritual performed to legitimize and exalt a king’s sovereignty and supreme status.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0e91d08190a4db907030955bb3 |
completed | March 22, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027b3ab408190ab1e68dfbcf7eec6 |
completed | March 22, 2026, 5:32 p.m. |
Created at: March 22, 2026, 3:32 p.m.