Triple
T13197057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sara Whitaker |
E314138
|
entity |
| Predicate | storyInvolvement |
P17462
|
FINISHED |
| Object | holiday chaos |
—
|
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: holiday chaos | Statement: [Sara Whitaker, storyInvolvement, holiday chaos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyInvolvement Context triple: [Sara Whitaker, storyInvolvement, holiday chaos]
-
A.
plotInvolvement
chosen
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
-
B.
narrativeThemeInvolvement
Indicates that an entity participates in or contributes to a particular narrative theme within a story or discourse.
-
C.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
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.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.