Triple
T9471356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connor Murphy |
E228396
|
entity |
| Predicate | drivesPlotDevice |
P36867
|
FINISHED |
| Object | misinterpreted letter |
—
|
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: misinterpreted letter | Statement: [Connor Murphy, drivesPlotDevice, misinterpreted letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesPlotDevice Context triple: [Connor Murphy, drivesPlotDevice, misinterpreted letter]
-
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.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
C.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
D.
drivesPlotElement
chosen
Indicates that one element of the narrative is a primary cause or motivator for the development, progression, or outcome of another plot element.
-
E.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fee13a88190b4532fb92ddaf401 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.