Triple
T16331603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deborah Kara Unger as Christine |
E396568
|
entity |
| Predicate | drivesNarrativeElement |
P35676
|
FINISHED |
| Object | suspense |
—
|
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: suspense | Statement: [Deborah Kara Unger as Christine, drivesNarrativeElement, suspense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesNarrativeElement Context triple: [Deborah Kara Unger as Christine, drivesNarrativeElement, suspense]
-
A.
isNarrativeDriven
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
-
B.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
narrativeAction
Indicates an action or event that advances, shapes, or affects the progression of a narrative or story.
-
D.
branchingNarrativeRole
Indicates the role an entity plays in determining or influencing the path or outcome within a branching or non-linear narrative structure.
-
E.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dfd9688190a749e48ebc055baf |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.