Triple
T4955828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murugan |
E111277
|
entity |
| Predicate | otherName |
P39
|
FINISHED |
| Object | Kumara |
E161604
|
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: Kumara | Statement: [Murugan, otherName, Kumara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumara Context triple: [Murugan, otherName, Kumara]
-
A.
Kumara
chosen
Kumara is another name for Kartikeya, the Hindu god of war and the son of Shiva and Parvati, widely revered in South India and Sri Lanka.
-
B.
Kunjara
Kunjara is an alternative name for the Fur language spoken by the Fur people of western Sudan.
-
C.
Rukmi
Rukmi is a character in Hindu mythology known as the proud and antagonistic brother of Rukmini, who opposed her marriage to Krishna.
-
D.
Kanak
The Kanak are the indigenous Melanesian people of New Caledonia, known for their distinct languages, customs, and long struggle for cultural recognition and political self-determination.
-
E.
Udaya
Udaya is a given name most notably associated with D. Udaya Kumar, the Indian designer who created the Indian rupee sign.
- 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.