Triple
T21993328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cal Morrison |
E543141
|
entity |
| Predicate | connectedToPlotElement |
P146205
|
FINISHED |
| Object | clone conspiracy |
—
|
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: clone conspiracy | Statement: [Cal Morrison, connectedToPlotElement, clone conspiracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToPlotElement Context triple: [Cal Morrison, connectedToPlotElement, clone conspiracy]
-
A.
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).
-
B.
enablesPlotElement
Indicates that one element of a narrative makes possible, sets up, or allows the occurrence of another specific plot element.
-
C.
introducesPlotElement
Indicates that an entity brings a new story component, twist, or development into the narrative.
-
D.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
E.
hasCommonPlotElement
Indicates that two narrative works share at least one similar or overlapping plot component, event, or storyline feature.
- F. None of above. chosen
Provenance (4 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1270f77fc8190aadcc02760d65ac0 |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:15 p.m.