Triple
T18452047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nala |
E450805
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | King of Nishadha |
—
|
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: King of Nishadha | Statement: [Nala, title, King of Nishadha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King of Nishadha Context triple: [Nala, title, King of Nishadha]
-
A.
King of Nishadha
chosen
King of Nishadha is a royal title in Hindu mythology held by Nala, the virtuous and skilled ruler famed from the Mahabharata.
-
B.
King of Panchala
King of Panchala is a royal title in the Indian epic Mahabharata, most notably held by Drupada, the ruler of the ancient kingdom of Panchala.
-
C.
King of Hastinapura
The King of Hastinapura is the sovereign ruler of the Kuru kingdom in the Indian epic Mahabharata, presiding over its capital city and royal lineage.
-
D.
King Varuna
King Varuna is a Vedic deity revered as the sovereign guardian of cosmic order, moral law, and the celestial waters in ancient Indian mythology.
-
E.
Navakasiga
Navakasiga is a village-level settlement located in the Bua Province on the northern island of Vanua Levu in Fiji.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264906cc8190b8b2cb77ec93d480 |
completed | April 19, 2026, 7 p.m. |
Created at: April 10, 2026, 11:31 a.m.