Triple
T28519487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wizard and Glass |
E721716
|
entity |
| Predicate | containsFrameStory |
P194654
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wizard and Glass, containsFrameStory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFrameStory Context triple: [Wizard and Glass, containsFrameStory, yes]
-
A.
settingOfFrameStory
Indicates that one entity serves as the narrative setting or contextual backdrop within which the frame story of another entity takes place.
-
B.
hasFramingStoryTitle
Indicates that an entity is associated with the title of a framing story that encloses or contextualizes its main narrative content.
-
C.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
D.
hasFictionalFrame
Indicates that one entity is presented or interpreted within the context of a fictional narrative, scenario, or imaginative framework provided by another entity.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: April 28, 2026, 3:19 a.m.