Triple
T24004732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Thumb |
E594339
|
entity |
| Predicate | storyElements |
P35676
|
FINISHED |
| Object | magic |
—
|
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: magic | Statement: [Tom Thumb, storyElements, magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyElements Context triple: [Tom Thumb, storyElements, magic]
-
A.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
C.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
D.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
E.
narrativeDesigner
Indicates a relationship where an entity serves as the creator or architect of a story’s structure, dialogue, and interactive narrative elements for another entity such as a game, experience, or project.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4681fd88190949c5c91d4f94910 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.