Triple
T20446324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirby: Squeak Squad |
E501526
|
entity |
| Predicate | storyPremise |
P44225
|
FINISHED |
| Object | Kirby pursues the Squeaks after they steal his cake |
—
|
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: Kirby pursues the Squeaks after they steal his cake | Statement: [Kirby: Squeak Squad, storyPremise, Kirby pursues the Squeaks after they steal his cake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyPremise Context triple: [Kirby: Squeak Squad, storyPremise, Kirby pursues the Squeaks after they steal his cake]
-
A.
narrativePremise
chosen
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
B.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
C.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
D.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cfd84c08190a3f971f1cd279715 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.