Triple
T902892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arjuna |
E19483
|
entity |
| Predicate | brother |
P363
|
FINISHED |
| Object | Nakula |
E115661
|
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: Nakula | Statement: [Arjuna, brother, Nakula]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakula Context triple: [Arjuna, brother, Nakula]
-
A.
Nakula
chosen
Nakula is a heroic prince in the Indian epic Mahabharata, renowned as one of the five Pandava brothers and celebrated for his exceptional skill in swordsmanship and horse-keeping.
-
B.
Bhima
Bhima is a powerful warrior prince from the Indian epic Mahabharata, renowned for his immense strength, loyalty, and pivotal role among the Pandava brothers.
-
C.
Sahadeva
Sahadeva is one of the five Pandava brothers in the Indian epic Mahabharata, renowned for his wisdom, knowledge of astrology, and loyalty.
-
D.
Karna
Karna is a legendary warrior and tragic hero of the Indian epic Mahabharata, renowned for his unmatched archery skills, unwavering loyalty, and complex moral dilemmas.
-
E.
Pandu
Pandu is a key figure in the Indian epic Mahabharata, the Kuru king and father of the Pandavas.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad56f4c08190a7a5091ff0eb3209 |
completed | March 1, 2026, 9:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac598e6ccc8190b0d75d36036f5e42 |
completed | March 7, 2026, 4:59 p.m. |
Created at: March 1, 2026, 7:39 p.m.