Triple
T20864728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Martin |
E513722
|
entity |
| Predicate | majorPlotEvent |
P71660
|
FINISHED |
| Object | escapes from prison |
—
|
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: escapes from prison | Statement: [Donald Martin, majorPlotEvent, escapes from prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPlotEvent Context triple: [Donald Martin, majorPlotEvent, escapes from prison]
-
A.
majorPlotPoint
chosen
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
B.
majorFlashpointIn
Indicates that an event, issue, or conflict serves as a primary source of tension or confrontation within a specified larger context or setting.
-
C.
centralPlotDevice
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
-
D.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
E.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45e51f08190ac1ff59280ad741b |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.