Triple
T18398866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vedic pantheon |
E449938
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Agni |
—
|
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: Agni | Statement: [Vedic pantheon, hasDeity, Agni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agni Context triple: [Vedic pantheon, 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.
Anyin Agni
Anyin Agni is a dialect of the Anyin language spoken by Agni communities, primarily in parts of Côte d’Ivoire and neighboring regions.
-
C.
Rudra
Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
-
D.
Vritra
Vritra is a powerful serpent or dragon-like demon in Hindu mythology, best known as the adversary slain by the god Indra to release the waters and restore cosmic order.
-
E.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518499b1481909c5de786c48faeba |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.