Triple
T19381455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yajnaseni |
E484818
|
entity |
| Predicate | bornIn |
P1
|
FINISHED |
| Object | Panchala |
E473849
|
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: Panchala | Statement: [Yajnaseni, bornIn, Panchala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Panchala Context triple: [Yajnaseni, bornIn, Panchala]
-
A.
Panchala
chosen
Panchala was an ancient Indian kingdom of the Mahabharata era, known for its powerful rulers and as the homeland of Draupadi.
-
B.
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.
-
C.
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.
-
D.
Charotar
Charotar is a fertile, culturally distinct region of central Gujarat in western India, known for its agrarian prosperity and significant diaspora.
-
E.
Magadha
Magadha was an ancient Indian kingdom and region in the eastern Gangetic plain that became a powerful political and cultural center, forming the core of several major empires.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a6075a88190aed7afa3b8fd3021 |
completed | April 20, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a072422e01481908d0e6233017be7f6 |
completed | May 15, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:35 p.m.