Triple
T8528571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | नारायण आप्टे |
E201882
|
entity |
| Predicate | संबंधित घटना |
P37
|
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.
関連事件
Indicates a relationship where one event is connected or related to another event, typically as part of the same case, incident, or context.
-
B.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
-
C.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
D.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
E.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe672e0588190a84328e1bf974f08 |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.