Triple
T29607894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innogen |
E754626
|
entity |
| Predicate | undergoesPlotDevice |
P103369
|
FINISHED |
| Object | false accusation of infidelity |
—
|
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: false accusation of infidelity | Statement: [Innogen, undergoesPlotDevice, false accusation of infidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoesPlotDevice Context triple: [Innogen, undergoesPlotDevice, false accusation of infidelity]
-
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.
majorPlotPoint
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
C.
partOfPlot
chosen
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
D.
storyTwist
Indicates an unexpected development or reversal that significantly changes the direction or understanding of a story’s events or relationships.
-
E.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 6:26 p.m.