Triple
T3367334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinayak Damodar Savarkar |
E70867
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vinayak |
E134673
|
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: Vinayak | Statement: [Vinayak Damodar Savarkar, givenName, Vinayak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vinayak Context triple: [Vinayak Damodar Savarkar, givenName, Vinayak]
-
A.
Shanmukha
Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
-
B.
Vinayaka
chosen
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.
-
C.
Nathuram
Nathuram was the Indian nationalist and Hindu extremist who assassinated Mahatma Gandhi in 1948.
-
D.
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.
-
E.
Nandiraj
Nandiraj is a tributary river that feeds into the Indravati River in central India.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2890480819082fe2e3c2874cece |
completed | March 8, 2026, 5:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3343664cc81909793820377b4bdc1 |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:13 p.m.