Triple
T20878633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Ticket contest |
E514085
|
entity |
| Predicate | centralRoleInPlot |
P21187
|
FINISHED |
| Object | inciting event |
—
|
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: inciting event | Statement: [Golden Ticket contest, centralRoleInPlot, inciting event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralRoleInPlot Context triple: [Golden Ticket contest, centralRoleInPlot, inciting event]
-
A.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
B.
centralPlotDevice
chosen
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
-
C.
politicalRoleInPlot
Indicates that an entity holds a specific political function, position, or influence within the context of a particular plot or storyline.
-
D.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
E.
plotInvolvement
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6775f108190a79cd5e8c31cecf6 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.