Triple
T941888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganesha |
E20323
|
entity |
| Predicate | sibling |
P363
|
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: [Ganesha, sibling, Skanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skanda Context triple: [Ganesha, sibling, 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.
Kubera
Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
-
D.
Indrajit
Indrajit is a powerful warrior prince in the Hindu epic Ramayana, famed for his mastery of celestial weapons and for being the formidable son of the demon king Ravana.
-
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 (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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a1a4888190997adf56eb761431 |
completed | March 1, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acddfeb918819083f948183aaaeb09 |
completed | March 8, 2026, 2:25 a.m. |
Created at: March 1, 2026, 7:40 p.m.