Triple
T5375171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakshmana |
E108942
|
entity |
| Predicate | killed |
P4646
|
FINISHED |
| Object | Indrajit |
E124408
|
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: Indrajit | Statement: [Lakshmana, killed, Indrajit]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Indrajit Context triple: [Lakshmana, killed, Indrajit]
-
A.
Indrajit
chosen
Indrajit is a powerful warrior prince in the Hindu epic Ramayana, famed for his mastery of celestial weapons and for being the formidable son of the demon king Ravana.
-
B.
Yudhajit
Yudhajit is a lesser-known prince in the Ramayana, recognized as the brother of Queen Kaikeyi and thus an uncle of Bharata.
-
C.
Shatrughna
Shatrughna is a prince of Ayodhya in the Hindu epic Ramayana, known as the devoted younger brother of Rama and the twin of Lakshmana.
-
D.
Ugrasena
Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
-
E.
Jayadratha
Jayadratha is a king from the Indian epic Mahabharata, best known for his role in the death of Abhimanyu and his subsequent slaying by Arjuna.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd86aed2a8819089d9e699f53563db |
completed | March 20, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf9f5885388190bf06b919425a81fe |
completed | March 22, 2026, 7:50 a.m. |
Created at: March 20, 2026, 2:03 p.m.