Triple
T17251929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Sesame |
E418775
|
entity |
| Predicate | narrativeEffect |
P126720
|
FINISHED |
| Object | creates sense of wonder |
—
|
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: creates sense of wonder | Statement: [Open Sesame, narrativeEffect, creates sense of wonder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeEffect Context triple: [Open Sesame, narrativeEffect, creates sense of wonder]
-
A.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
B.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
C.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
D.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
E.
narrativeAction
Indicates an action or event that advances, shapes, or affects the progression of a narrative or story.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e694f788190a1c86e95264ed2fe |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:39 a.m.