Triple
T5131714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shukla Yajurveda |
E115714
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Agni |
E102074
|
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: Agni | Statement: [Shukla Yajurveda, hasDeity, Agni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agni Context triple: [Shukla Yajurveda, hasDeity, Agni]
-
A.
Agni
chosen
Agni is the Vedic god of fire, revered as a central deity of sacrifice and a divine messenger between humans and the gods in ancient Indian religion.
-
B.
Rudra
Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
-
C.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
-
D.
Vivasvan
Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
-
E.
Vrushabhadri
Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd782904788190b544540483915c0e |
completed | March 20, 2026, 4:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec4c626a48190b2fd81b88b5a59cc |
completed | March 21, 2026, 4:18 p.m. |
Created at: March 20, 2026, 1:42 p.m.