Triple
T29032705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Marston |
E737769
|
entity |
| Predicate | deathOrderInStory |
P27931
|
FINISHED |
| Object | early 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: early victim | Statement: [Anthony Marston, deathOrderInStory, early victim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathOrderInStory Context triple: [Anthony Marston, deathOrderInStory, early victim]
-
A.
diesInAct
Indicates that an entity dies during the course of a specified action or event.
-
B.
deathBefore
chosen
Indicates that one entity’s death occurred earlier in time than another entity’s death.
-
C.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
D.
ordersDeathOf
Indicates that one entity commands or authorizes the killing or execution of another entity.
-
E.
deathNarrativeFunction
Indicates that a character’s death serves a specific narrative role or function within the story’s structure or themes.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 9:56 a.m.