Triple
T22033568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drishyam 2 |
E544144
|
entity |
| Predicate | hasPrequelEvent |
P11018
|
FINISHED |
| Object | killing of Sam Deshmukh |
—
|
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: killing of Sam Deshmukh | Statement: [Drishyam 2, hasPrequelEvent, killing of Sam Deshmukh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrequelEvent Context triple: [Drishyam 2, hasPrequelEvent, killing of Sam Deshmukh]
-
A.
hasPrecedingEvents
chosen
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
B.
isPrequelTo
Indicates that one work or event occurs earlier in time and narratively sets up or leads into another work or event.
-
C.
hasAnimatedPrequel
Indicates that one work serves as an earlier, animated installment in the narrative or release sequence of another work.
-
D.
prequelOrSequelTo
Indicates that one work in a narrative series occurs earlier or later in the storyline or release order relative to another work, as its prequel or sequel.
-
E.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ef97348190b8dcdcad11694ebe |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.