Triple
T22602232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Lacey |
E574856
|
entity |
| Predicate | definingPlotElement |
P63936
|
FINISHED |
| Object | recent divorce |
—
|
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: recent divorce | Statement: [John Lacey, definingPlotElement, recent divorce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definingPlotElement Context triple: [John Lacey, definingPlotElement, recent divorce]
-
A.
enablesPlotElement
Indicates that one element of a narrative makes possible, sets up, or allows the occurrence of another specific plot element.
-
B.
introducesPlotElement
Indicates that an entity brings a new story component, twist, or development into the narrative.
-
C.
plotElement
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).
-
D.
connectedToPlotElement
Indicates that one element is linked or related to a specific plot element within a narrative structure.
-
E.
definingTraitInPlot
chosen
Indicates that a particular trait of an entity plays a defining or pivotal role in the development or outcome of the plot.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626eb178819096866d03a78f82fc |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.