Triple
T22092719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Slow Fire Burning |
E545948
|
entity |
| Predicate | hasMurderVictim |
P116503
|
FINISHED |
| Object | young man found dead on a houseboat |
—
|
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: young man found dead on a houseboat | Statement: [A Slow Fire Burning, hasMurderVictim, young man found dead on a houseboat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMurderVictim Context triple: [A Slow Fire Burning, hasMurderVictim, young man found dead on a houseboat]
-
A.
hasMurderVictimCharacter
chosen
Indicates that an entity (such as a work of fiction or event) includes or involves a character who is the victim of a murder.
-
B.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
-
C.
murderVictimOf
Indicates that one entity is the person who was killed by another entity in an act of murder.
-
D.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
-
E.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e6b1d881909bf0f4a52199354c |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.