Triple
T13895481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasi Kingdom |
E334075
|
entity |
| Predicate | neighboringEntity |
P350
|
FINISHED |
| Object | Kosala |
E449560
|
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: Kosala | Statement: [Kasi Kingdom, neighboringEntity, Kosala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kosala Context triple: [Kasi Kingdom, neighboringEntity, 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.
Kosala kingdom
The Kosala kingdom was an ancient Indian realm in the Ganges plain, prominent in Hindu epics and early Buddhist texts as a major political and cultural center.
-
E.
Uttaradit
Uttaradit is a provincial capital in northern Thailand known as a regional transport hub and gateway to nearby historical and natural attractions.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1c0b6848190b67051e0ccbdb707 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:15 p.m.