Triple
T35071969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culla Holme |
E1011902
|
entity |
| Predicate | plotImpact |
P129750
|
FINISHED |
| Object | sets the tragic narrative in motion |
—
|
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: sets the tragic narrative in motion | Statement: [Culla Holme, plotImpact, sets the tragic narrative in motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotImpact Context triple: [Culla Holme, plotImpact, sets the tragic narrative in motion]
-
A.
exportImpact
Indicates the effect or consequences that an entity’s exports have on another entity, system, or context.
-
B.
chartImpact
Indicates how one factor or action influences the shape, position, or behavior of a chart or graphical representation.
-
C.
encodingImpact
Indicates how one encoding or encoding choice affects, modifies, or constrains another process, representation, or outcome.
-
D.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
E.
narrativeImpactOn
chosen
Indicates how one element influences, shapes, or alters the narrative significance or storyline of another.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.