Triple
T23240130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsya |
E581416
|
entity |
| Predicate | neighboringEntity |
P350
|
FINISHED |
| Object | Panchala |
—
|
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: Panchala | Statement: [Matsya, neighboringEntity, Panchala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Panchala Context triple: [Matsya, neighboringEntity, 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.
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.
Charotar
Charotar is a fertile, culturally distinct region of central Gujarat in western India, known for its agrarian prosperity and significant diaspora.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ecc7e481908cac59df5c0deea1 |
completed | April 29, 2026, 5:11 a.m. |
Created at: April 17, 2026, 4:10 p.m.