Triple

T7368778
Position Surface form Disambiguated ID Type / Status
Subject Shanmukha E169937 entity
Predicate hasAlternativeName 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: [Shanmukha, hasAlternativeName, Kartikeya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kartikeya
Context triple: [Shanmukha, hasAlternativeName, 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. Indra
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • D. Kubera
    Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
  • E. Rudra
    Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
  • 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f17fe278819094eb1dd886583c6a completed March 27, 2026, 9:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8b4e3181481909eec1a09ae295923 completed March 29, 2026, 5:13 a.m.
Created at: March 27, 2026, 3:07 p.m.