Triple
T26739053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Once Upon a Time Adventure |
E674192
|
entity |
| Predicate | usesStorytellingForm |
P35682
|
FINISHED |
| Object | fairy tale narrative |
—
|
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: fairy tale narrative | Statement: [Once Upon a Time Adventure, usesStorytellingForm, fairy tale narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorytellingForm Context triple: [Once Upon a Time Adventure, usesStorytellingForm, fairy tale narrative]
-
A.
narrativeFormat
chosen
Indicates the specific structural or stylistic form in which a narrative is presented or expressed.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
modeOfTelling
Indicates the manner or medium through which something is narrated, communicated, or expressed.
-
D.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
E.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:48 a.m.