Triple
T26701322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPH4 |
E673161
|
entity |
| Predicate | enablesPlotEvent |
P111237
|
FINISHED |
| Object | Lucys transformation into post-human entity |
—
|
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: Lucys transformation into post-human entity | Statement: [CPH4, enablesPlotEvent, Lucys transformation into post-human entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesPlotEvent Context triple: [CPH4, enablesPlotEvent, Lucys transformation into post-human entity]
-
A.
enablesPlotElement
chosen
Indicates that one element of a narrative makes possible, sets up, or allows the occurrence of another specific plot element.
-
B.
exposesEvent
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
-
C.
connectedToPlotElement
Indicates that one element is linked or related to a specific plot element within a narrative structure.
-
D.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:31 a.m.