Triple
T20965356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satanika |
E516351
|
entity |
| Predicate | cousin |
P1999
|
FINISHED |
| Object | Prativindhya |
—
|
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: Prativindhya | Statement: [Satanika, cousin, Prativindhya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prativindhya Context triple: [Satanika, cousin, Prativindhya]
-
A.
Prativindhya
chosen
Prativindhya is a character in the Indian epic Mahabharata, known as the son of Arjuna and Draupadi and one of the Upapandavas.
-
B.
Trinavarta
Trinavarta is a whirlwind demon in Hindu mythology who attempts to kill the infant Krishna by carrying him off into the sky, only to be destroyed by him.
-
C.
Thasra
Thasra is a town located in the Kheda district of the Indian state of Gujarat.
-
D.
Sairandhri
Sairandhri is the assumed incognito identity of Draupadi during the Pandavas’ year of exile in the Hindu epic Mahabharata.
-
E.
Vrishni
Vrishni was a prominent clan within the ancient Yadava lineage of India, traditionally associated with Lord Krishna and centered around the region of Mathura and Dvaraka.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 1:32 p.m.