Triple
T17937635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satvata |
E448508
|
entity |
| Predicate | relatedGroup |
P37
|
FINISHED |
| Object | Vrishni |
—
|
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: Vrishni | Statement: [Satvata, relatedGroup, Vrishni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vrishni Context triple: [Satvata, relatedGroup, Vrishni]
-
A.
Vrishni
chosen
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.
-
B.
Devaka
Devaka is a figure in Hindu tradition known primarily as the father of Devaki, the mother of the deity Krishna.
-
C.
Vrikodara
Vrikodara is a famous epithet of Bhima, the mighty Pandava hero of the Indian epic Mahabharata, highlighting his immense strength and voracious appetite.
-
D.
Vaishvanara
Vaishvanara is a Vedic epithet of the fire god Agni, emphasizing his universal, all-pervading aspect as the cosmic fire present in all beings.
-
E.
Yaudheya
Yaudheya is a relatively lesser-known figure in the Mahabharata tradition, remembered primarily as a son of the Pandava king Yudhishthira.
- 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.