Triple
T11430734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be Our Guest |
E270870
|
entity |
| Predicate | narrativePointInPlot |
P79415
|
FINISHED |
| Object | Belle's first dinner in the castle |
—
|
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: Belle's first dinner in the castle | Statement: [Be Our Guest, narrativePointInPlot, Belle's first dinner in the castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativePointInPlot Context triple: [Be Our Guest, narrativePointInPlot, Belle's first dinner in the castle]
-
A.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
B.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
C.
majorPlotPoint
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
D.
narrativeMoment
chosen
Indicates the specific point or phase within a narrative at which an event, action, or relationship occurs.
-
E.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c1bfb881909720c74fe0fa837f |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.