Triple
T23943018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kym Buchman |
E602838
|
entity |
| Predicate | storyArcInvolves |
P24126
|
FINISHED |
| Object | confronting past trauma |
—
|
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: confronting past trauma | Statement: [Kym Buchman, storyArcInvolves, confronting past trauma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyArcInvolves Context triple: [Kym Buchman, storyArcInvolves, confronting past trauma]
-
A.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
B.
storyArcLength
Indicates the duration or extent of a narrative arc within a story, such as how long a particular plotline continues.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
stakesInStory
Indicates that one entity has a personal investment, risk, or potential gain/loss tied to the outcome of another entity’s story or narrative.
-
E.
storyline
chosen
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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02bf38081909c99b98e04a8d2aa |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:10 p.m.