Triple
T23349437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackgate Penitentiary |
E591963
|
entity |
| Predicate | frequentPlotElement |
P2762
|
FINISHED |
| Object | prison breaks |
—
|
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: prison breaks | Statement: [Blackgate Penitentiary, frequentPlotElement, prison breaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentPlotElement Context triple: [Blackgate Penitentiary, frequentPlotElement, prison breaks]
-
A.
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).
-
B.
connectedToPlotElement
Indicates that one element is linked or related to a specific plot element within a narrative structure.
-
C.
drivesPlotElement
Indicates that one element of the narrative is a primary cause or motivator for the development, progression, or outcome of another plot element.
-
D.
introducesPlotElement
Indicates that an entity brings a new story component, twist, or development into the narrative.
-
E.
enablesPlotElement
Indicates that one element of a narrative makes possible, sets up, or allows the occurrence of another specific plot element.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f199cb2a3c8190a5c0c8d8735256c7 |
completed | April 29, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.