Triple
T23217801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahadeva |
E580797
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Kartikeya |
—
|
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: Kartikeya | Statement: [Mahadeva, fatherOf, Kartikeya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kartikeya Context triple: [Mahadeva, fatherOf, Kartikeya]
-
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.
Pradyumna
Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
-
C.
Purushottama Deva
Purushottama Deva was a prominent 15th-century king of Odisha known for expanding the Gajapati Empire and patronizing the Jagannath cult and temple architecture.
-
D.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
-
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 (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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916653f08190a7dcbc659c6b6a25 |
completed | April 29, 2026, 5:04 a.m. |
Created at: April 17, 2026, 4:08 p.m.