Triple
T4512079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soma |
E102075
|
entity |
| Predicate | associatedDeity |
P1481
|
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: [Soma, associatedDeity, Agni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agni Context triple: [Soma, associatedDeity, 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.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
-
C.
Yagnik
Yagnik is an Indian surname commonly associated with Gujarati families and notable figures in politics, arts, and public life.
-
D.
Vayu
Vayu is the Hindu god of wind, revered as a powerful Vedic deity and divine father of the monkey-god Hanuman.
-
E.
Varuna
Varuna is a large, rapidly rotating trans-Neptunian object in the Kuiper Belt, notable for its elongated shape and classification as a likely dwarf-planet candidate.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd571412788190a374abd1e05519e4 |
completed | March 20, 2026, 2:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bd7f875c4c81909e67d44b605816c2 |
completed | March 20, 2026, 5:10 p.m. |
Created at: March 20, 2026, 1:01 p.m.