Triple
T19963171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aja |
E479865
|
entity |
| Predicate | ruled |
P760
|
FINISHED |
| Object | Kosala |
—
|
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: Kosala | Statement: [Aja, ruled, Kosala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kosala Context triple: [Aja, ruled, Kosala]
-
A.
Kosala
chosen
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.
-
B.
Panchala
Panchala was an ancient Indian kingdom of the Mahabharata era, known for its powerful rulers and as the homeland of Draupadi.
-
C.
Kishkindha
Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
-
D.
Karkotaka
Karkotaka is a serpent king in Hindu mythology, known for his role in the legends of King Nala and his association with curses and transformation.
-
E.
Kishkindha region
The Kishkindha region is the legendary monkey kingdom in the Indian epic Ramayana, ruled by Sugriva and central to Rama’s alliance with the Vanara army.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af619108190825cbcfb6b8e1fa5 |
completed | April 20, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:54 p.m.