Triple
T18540237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaishampayana |
E453075
|
entity |
| Predicate | guruParampara |
P22248
|
FINISHED |
| Object | disciple of Vyasa in the Vedic tradition |
—
|
LITERAL FINISHED |
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: disciple of Vyasa in the Vedic tradition | Statement: [Vaishampayana, guruParampara, disciple of Vyasa in the Vedic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guruParampara Context triple: [Vaishampayana, guruParampara, disciple of Vyasa in the Vedic tradition]
-
A.
guru
chosen
Indicates that one entity serves as a spiritual teacher, guide, or mentor to another entity.
-
B.
numberOfGurus
Indicates the quantity or count of gurus associated with a given entity or context.
-
C.
wasGuruResidenceOf
Indicates that a particular place served as the residence of a specific guru.
-
D.
currentMahant
Indicates that the subject is the person who currently holds the position or role of Mahant (head or chief) of the referenced religious institution or community.
-
E.
fifthGuruOfSikhs
Indicates that one entity is the fifth spiritual leader (Guru) in the historical succession of Sikh Gurus in relation to the Sikh community.
- F. None of above.
Provenance (3 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b64178819082861a03fd067095 |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.