Triple
T1560411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | नाथूराम विनायक गोडसे |
E33307
|
entity |
| Predicate | प्रसिद्ध_के_लिए |
P22
|
FINISHED |
| Object | महात्मा गांधी की हत्या |
—
|
LITERAL 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: महात्मा गांधी की हत्या | Statement: [नाथूराम विनायक गोडसे, प्रसिद्ध_के_लिए, महात्मा गांधी की हत्या]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: प्रसिद्ध_के_लिए Context triple: [नाथूराम विनायक गोडसे, प्रसिद्ध_के_लिए, महात्मा गांधी की हत्या]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
C.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
D.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
E.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- F. None of above.
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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.