Triple
T4512018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agni |
E102074
|
entity |
| Predicate | offspring |
P980
|
FINISHED |
| Object | Skanda |
E31785
|
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: Skanda | Statement: [Agni, offspring, Skanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skanda Context triple: [Agni, offspring, Skanda]
-
A.
Kartikeya
chosen
Kartikeya is a Hindu war god, traditionally depicted as a youthful, spear-wielding deity and revered as the son of Shiva and Parvati.
-
B.
Narasimha
Narasimha is the fierce man-lion incarnation of the Hindu god Vishnu, known for destroying the demon king Hiranyakashipu to protect his devotee Prahlada.
-
C.
Shanmukha
Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
-
D.
Karpagambal
Karpagambal is the Hindu goddess Parvati worshipped as the consort of Lord Shiva at the Kapaleeshwarar Temple in Mylapore, Chennai.
-
E.
Kubera
Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
- 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.