Triple
T18477488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satyaki |
E451469
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Yadava |
—
|
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: Yadava | Statement: [Satyaki, ethnicGroup, Yadava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yadava Context triple: [Satyaki, ethnicGroup, Yadava]
-
A.
Yadava
chosen
Yadava refers to the ancient Indo-Aryan clan or community traditionally regarded as the lineage of King Yadu and prominently associated with the Hindu deity Krishna.
-
B.
Yadu
Yadu is a legendary king in Hindu mythology regarded as the progenitor of the Yadava clan, to which figures like Krishna belong.
-
C.
Parmar
Parmar is a surname of Indian origin, commonly associated with various communities and regions in India.
-
D.
Yadava people
The Yadava people are an ancient Indo-Aryan community of the Indian subcontinent traditionally associated with pastoralism, warrior lineages, and the legendary clan of the deity Krishna.
-
E.
Solanki
Solanki refers to a prominent medieval Indian Rajput dynasty that ruled parts of present-day Gujarat and surrounding regions, noted for its patronage of art, architecture, and temple construction.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53064a7548190b712a14ad0c7a477 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:35 a.m.