Triple
T17937588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhaka |
E448507
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Uddhava |
—
|
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: Uddhava | Statement: [Andhaka, hasMember, Uddhava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uddhava Context triple: [Andhaka, hasMember, Uddhava]
-
A.
Uddhava
chosen
Uddhava is a prominent figure in Hindu mythology, known as a close friend and wise counselor of Krishna in the Yadava dynasty.
-
B.
Pradyumna
Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
-
C.
Aniruddha
Aniruddha is a prominent figure in Hindu mythology, known as the grandson of Krishna and a heroic member of the Yadava dynasty.
-
D.
Sahadeva
Sahadeva is one of the five Pandava brothers in the Indian epic Mahabharata, renowned for his wisdom, knowledge of astrology, and loyalty.
-
E.
Anjaneya
Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad937f0881909d22ac8c2be9e35e |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.