Triple
T4955824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murugan |
E111277
|
entity |
| Predicate | otherName |
P39
|
FINISHED |
| Object | Kartikeya |
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: Kartikeya | Statement: [Murugan, otherName, Kartikeya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kartikeya Context triple: [Murugan, otherName, 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.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
-
C.
Kubera
Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
-
D.
Aniruddha
Aniruddha is a prominent figure in Hindu mythology, known as the grandson of Krishna and a heroic member of the Yadava dynasty.
-
E.
Vinayaka
Vinayaka is another name for the Hindu deity Ganesha, the elephant-headed god revered as the remover of obstacles and patron of wisdom and beginnings.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71babb44819085b4cd4864433e79 |
completed | March 20, 2026, 4:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81de17748190a26abda7d3703b8e |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:32 p.m.