Triple
T22451311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keller factory |
E554996
|
entity |
| Predicate | connectedToPlotPoint |
P10008
|
FINISHED |
| Object | Joe Keller’s exoneration in court |
—
|
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: Joe Keller’s exoneration in court | Statement: [Keller factory, connectedToPlotPoint, Joe Keller’s exoneration in court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToPlotPoint Context triple: [Keller factory, connectedToPlotPoint, Joe Keller’s exoneration in court]
-
A.
connectedToPlotElement
Indicates that one element is linked or related to a specific plot element within a narrative structure.
-
B.
connectedToEvent
chosen
Indicates that an entity has a direct association or linkage with a specific event.
-
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.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
E.
connectedToPlace
Indicates that one entity has a spatial, functional, or relational link or association with a specific place.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ba6a88190a0a79e2c20fa8c08 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.