Triple
T15032648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin |
E378390
|
entity |
| Predicate | storyStartsWith |
P21329
|
FINISHED |
| Object | discovery of a time portal in his bedroom |
—
|
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: discovery of a time portal in his bedroom | Statement: [Kevin, storyStartsWith, discovery of a time portal in his bedroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyStartsWith Context triple: [Kevin, storyStartsWith, discovery of a time portal in his bedroom]
-
A.
narrativeStart
chosen
Indicates the point or event at which a narrative, story, or sequence of events begins.
-
B.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e3a7c8819081f26c2435c1bcb2 |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:59 a.m.