Triple
T32125533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaffer Conservatory |
E820489
|
entity |
| Predicate | settingFunctionInPlot |
P32087
|
FINISHED |
| Object | primary setting of Whiplash |
—
|
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: primary setting of Whiplash | Statement: [Shaffer Conservatory, settingFunctionInPlot, primary setting of Whiplash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingFunctionInPlot Context triple: [Shaffer Conservatory, settingFunctionInPlot, primary setting of Whiplash]
-
A.
enablesPlotElement
Indicates that one element of a narrative makes possible, sets up, or allows the occurrence of another specific plot element.
-
B.
hasFunctionInPlot
chosen
Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
-
C.
settingOfControl
Indicates that one entity is the context or environment in which another entity exercises control or governance.
-
D.
coordinatesFunction
Indicates a relationship where one entity organizes, schedules, or manages the execution of a function or activity involving other entities.
-
E.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:29 a.m.