Triple
T1560437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | नाथूराम विनायक गोडसे |
E33307
|
entity |
| Predicate | लिखित_कृति |
P2831
|
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.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
notableWorkWrittenThere
Indicates that a notable work was written at or in the specified place.
-
C.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
D.
wrote
chosen
Indicates that an entity is the author or creator of a written work involving another entity.
-
E.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
- 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.