Triple
T10809271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Ballantyne |
E255052
|
entity |
| Predicate | involvesPlotElement |
P2762
|
FINISHED |
| Object | murder investigation |
—
|
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: murder investigation | Statement: [John Ballantyne, involvesPlotElement, murder investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPlotElement Context triple: [John Ballantyne, involvesPlotElement, murder investigation]
-
A.
plotInvolvement
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
-
B.
plotElement
chosen
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
C.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
D.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b60c6481909b043565a65f996d |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.