Triple
T4519784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyasa |
E103237
|
entity |
| Predicate | organized |
P123
|
FINISHED |
| Object | Samaveda |
E19932
|
NE 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: Samaveda | Statement: [Vyasa, organized, Samaveda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samaveda Context triple: [Vyasa, organized, Samaveda]
-
A.
Samaveda
chosen
Samaveda is one of the four Vedas of ancient Indian scripture, primarily consisting of melodies and chants used in Vedic rituals and early Hindu liturgy.
-
B.
Atharvaveda
Atharvaveda is one of the four Vedas of Hinduism, comprising hymns, spells, and rituals dealing with everyday life, healing, and protection.
-
C.
Yajurveda
Yajurveda is one of the four principal Vedas of Hinduism, primarily focused on prose mantras and ritual formulas used in sacrificial ceremonies.
-
D.
Shukla Yajurveda
Shukla Yajurveda is one of the two main recensions of the Yajurveda, characterized by its clear separation of mantras and explanatory prose used in Vedic ritual.
-
E.
Jatavedas
Jatavedas is a prominent Vedic epithet of the fire god Agni, highlighting his all-knowing, all-consuming nature as the divine flame that permeates and witnesses all.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5747e90c81908fa112ecace699a9 |
completed | March 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be67b09ed88190b72263c4dd5716b3 |
completed | March 21, 2026, 9:41 a.m. |
Created at: March 20, 2026, 1:02 p.m.