Triple
T8827389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortunato |
E210048
|
entity |
| Predicate | storyThemeContext |
P73134
|
FINISHED |
| Object | revenge |
—
|
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: revenge | Statement: [Fortunato, storyThemeContext, revenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyThemeContext Context triple: [Fortunato, storyThemeContext, revenge]
-
A.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
C.
dramaticTheme
chosen
Indicates that a work, scene, or narrative centers around a particular dramatic subject, motif, or emotional conflict as its main thematic focus.
-
D.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
E.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6034e8dc819099116d772e87569a |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.