Triple
T902391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yajurveda |
E19474
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Atharvaveda |
E20131
|
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: Atharvaveda | Statement: [Yajurveda, relatedTo, Atharvaveda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atharvaveda Context triple: [Yajurveda, relatedTo, Atharvaveda]
-
A.
Atharvaveda
chosen
Atharvaveda is one of the four Vedas of Hinduism, comprising hymns, spells, and rituals dealing with everyday life, healing, and protection.
-
B.
Yajurveda
Yajurveda is one of the four principal Vedas of Hinduism, primarily focused on prose mantras and ritual formulas used in sacrificial ceremonies.
-
C.
Samaveda
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.
-
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.
Rigveda
The Rigveda is the oldest of the four Vedas, a foundational collection of ancient Sanskrit hymns that form a core sacred text of Hinduism.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad56f4c08190a7a5091ff0eb3209 |
completed | March 1, 2026, 9:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac3b9b7eb88190b7fa4f9dbcc73d64 |
completed | March 7, 2026, 2:52 p.m. |
Created at: March 1, 2026, 7:39 p.m.