Triple
T18958195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Starks |
E463835
|
entity |
| Predicate | centralPlotFunction |
P88311
|
FINISHED |
| Object | attempts to change the future |
—
|
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: attempts to change the future | Statement: [Jack Starks, centralPlotFunction, attempts to change the future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlotFunction Context triple: [Jack Starks, centralPlotFunction, attempts to change the future]
-
A.
centralPlotDevice
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
-
B.
primaryFunctionInPlot
chosen
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
C.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
D.
majorPlotPoint
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
E.
centralScene
Indicates that one scene functions as the main or focal scene within a larger narrative, sequence, or composition.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d057a48190b82b5788b3281e28 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon