Triple
T864238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Way We Live Now |
E18664
|
entity |
| Predicate | centralPlotElement |
P2762
|
FINISHED |
| Object | fraudulent railway scheme |
—
|
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: fraudulent railway scheme | Statement: [The Way We Live Now, centralPlotElement, fraudulent railway scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlotElement Context triple: [The Way We Live Now, centralPlotElement, fraudulent railway scheme]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
C.
centralText
Indicates that one text element is positioned or designated as the central or primary text relative to surrounding content or layout.
-
D.
plotElement
chosen
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).
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6956488190a5644cdd5b55684f |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.