Triple
T2172517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ruby slippers |
E48457
|
entity |
| Predicate | functionInStory |
P7328
|
FINISHED |
| Object | enable travel to and from the Land of Oz |
—
|
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: enable travel to and from the Land of Oz | Statement: [ruby slippers, functionInStory, enable travel to and from the Land of Oz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInStory Context triple: [ruby slippers, functionInStory, enable travel to and from the Land of Oz]
-
A.
storyFunction
chosen
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
E.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.