Triple
T32936638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burned |
E842545
|
entity |
| Predicate | hasPlotStructure |
P105753
|
FINISHED |
| Object | whodunit 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: whodunit investigation | Statement: [Burned, hasPlotStructure, whodunit investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlotStructure Context triple: [Burned, hasPlotStructure, whodunit investigation]
-
A.
hasDramaticStructure
Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
-
B.
hasPlot
chosen
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
C.
hasMinimalPlot
Indicates that a work’s storyline is very simple, sparse, or lacking in substantial narrative development.
-
D.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
E.
hasFilmStructure
Indicates that one entity possesses or is organized according to the narrative or formal structure of a film.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:20 a.m.