Triple
T32341596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nan Adams |
E826330
|
entity |
| Predicate | storyTwist |
P178357
|
FINISHED |
| Object | she has been dead since the beginning of the journey |
—
|
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: she has been dead since the beginning of the journey | Statement: [Nan Adams, storyTwist, she has been dead since the beginning of the journey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyTwist Context triple: [Nan Adams, storyTwist, she has been dead since the beginning of the journey]
-
A.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
C.
storyline
Indicates that one entity serves as the narrative plot or sequence of events 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.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: May 1, 2026, 12:48 a.m.