Triple
T22574314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V/H/S |
E544351
|
entity |
| Predicate | mainSettingOfFramingStory |
P45019
|
FINISHED |
| Object | house |
—
|
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: house | Statement: [V/H/S, mainSettingOfFramingStory, house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettingOfFramingStory Context triple: [V/H/S, mainSettingOfFramingStory, house]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
narrativeFrameWork
Indicates a relationship where one element provides the structural or conceptual framework within which another element’s narrative is organized, interpreted, or presented.
-
C.
narrativeSettingOfWork
chosen
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
D.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fec296481908a6101b02e5bedaa |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.