Triple
T36388314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Connell |
E896258
|
entity |
| Predicate | isCharacterInPlotDevice |
P52203
|
FINISHED |
| Object | murder victim |
—
|
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: murder victim | Statement: [Kay Connell, isCharacterInPlotDevice, murder victim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacterInPlotDevice Context triple: [Kay Connell, isCharacterInPlotDevice, murder victim]
-
A.
isPivotalForCharacter
Indicates that something plays a crucial, defining role in shaping a character’s development, decisions, or narrative arc.
-
B.
isCharacterInSetting
Indicates that a particular character appears or exists within a specified setting or environment.
-
C.
isCharacterInWork
Indicates that a particular character appears in or is part of a specified creative work (such as a book, film, or game).
-
D.
characterStatusInStory
chosen
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
E.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.