Triple
T5647113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishkindha |
E124411
|
entity |
| Predicate | successorRuler |
P45012
|
FINISHED |
| Object | Angada |
E470323
|
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: Angada | Statement: [Kishkindha, successorRuler, Angada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Angada Context triple: [Kishkindha, successorRuler, Angada]
-
A.
Angada
chosen
Angada is a heroic Vanara prince in the Indian epic Ramayana, renowned for his loyalty to Rama and his role in the war against Ravana.
-
B.
Bhailsa
Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
-
C.
Bezawada
Bezawada is the traditional name and popular local nickname for the city of Vijayawada in the Indian state of Andhra Pradesh.
-
D.
Orya
Orya is the ISO 15924 script code representing the Odia script used for writing the Odia language of eastern India.
-
E.
Kosala
Kosala is an ancient Indian kingdom in Hindu epic tradition, most prominently known as the realm ruled by Lord Rama with its capital at Ayodhya.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022abf0108190b10b3a9fe1688bf9 |
completed | March 22, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a1d7af8819092e28ce9fb14d1f1 |
completed | March 22, 2026, 9:07 p.m. |
Created at: March 22, 2026, 3:41 p.m.