Triple
T19963164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aja |
E479865
|
entity |
| Predicate | grandfatherOf |
P979
|
FINISHED |
| Object | Lakshmana |
—
|
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: Lakshmana | Statement: [Aja, grandfatherOf, Lakshmana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lakshmana Context triple: [Aja, grandfatherOf, Lakshmana]
-
A.
Lakshmana
chosen
Lakshmana is a devoted younger brother of Rama in the Hindu epic Ramayana, renowned for his unwavering loyalty, courage, and selfless service.
-
B.
Lakshmana Kumara
Lakshmana Kumara is a relatively obscure figure in the Mahabharata, known primarily as the nephew of the Kuru teacher Kripa.
-
C.
Vibhishana
Vibhishana is a virtuous rakshasa prince in the Hindu epic Ramayana, known for abandoning his brother Ravana to ally with Rama and uphold dharma.
-
D.
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.
-
E.
Bhima
Bhima is a major river in western India that flows through the states of Maharashtra, Karnataka, and Telangana before joining the Krishna River.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af619108190825cbcfb6b8e1fa5 |
completed | April 20, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:54 p.m.