Triple
T6971369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saravanabhava |
E161605
|
entity |
| Predicate | refersTo |
P37
|
FINISHED |
| Object | Subrahmanya |
E164754
|
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: Subrahmanya | Statement: [Saravanabhava, refersTo, Subrahmanya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Subrahmanya Context triple: [Saravanabhava, refersTo, Subrahmanya]
-
A.
Sitarama
Sitarama is a revered epithet of the Hindu deity Rama that emphasizes his inseparable union with his consort Sita and their ideal of divine marital devotion.
-
B.
Shanmukha
Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
-
C.
Karpagambal
Karpagambal is the Hindu goddess Parvati worshipped as the consort of Lord Shiva at the Kapaleeshwarar Temple in Mylapore, Chennai.
-
D.
Subramanya
chosen
Subramanya is a Hindu deity of war and wisdom, widely revered in South India and identified with the god Kartikeya (Murugan).
-
E.
Narayana
Narayana is a revered name of the Hindu god Vishnu, especially associated with his role as the supreme preserver and sustainer of the universe.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db38013081908037d23843dccad7 |
completed | March 27, 2026, 7:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c794318fb08190a9a89570b2a6999b |
completed | March 28, 2026, 8:41 a.m. |
Created at: March 27, 2026, 2:30 p.m.