Triple
T4523708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishma Parva |
E103325
|
entity |
| Predicate | narrator |
P2181
|
FINISHED |
| Object | Sanjaya |
E102167
|
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: Sanjaya | Statement: [Bhishma Parva, narrator, Sanjaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sanjaya Context triple: [Bhishma Parva, narrator, Sanjaya]
-
A.
Sanjaya
Sanjaya was an early Javanese king traditionally regarded as the founder of the Mataram (Medang) Kingdom and the Sanjaya dynasty in Central Java.
-
B.
Sanjaya
chosen
Sanjaya is the charioteer and seer in the Mahabharata who, granted divine vision, narrates the events of the Kurukshetra war to the blind king Dhritarashtra.
-
C.
Ugrasena
Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
-
D.
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.
-
E.
Pavanputra
Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574d7c2481909049955ca47613a6 |
completed | March 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdd37f7ed48190ae0a82597aafc66e |
completed | March 20, 2026, 11:08 p.m. |
Created at: March 20, 2026, 1:03 p.m.