Triple
T22102209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arsenal Stadium Mystery |
E546197
|
entity |
| Predicate | hasTypeOfMurderMethod |
P128435
|
FINISHED |
| Object | poisoning |
—
|
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: poisoning | Statement: [The Arsenal Stadium Mystery, hasTypeOfMurderMethod, poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfMurderMethod Context triple: [The Arsenal Stadium Mystery, hasTypeOfMurderMethod, poisoning]
-
A.
methodOfMurderScheme
chosen
Indicates the specific method or scheme by which a murder is carried out in a given situation or plan.
-
B.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
-
C.
hasPartInMurderOf
Indicates involvement as a contributing participant in the commission of a murder.
-
D.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129163b908190b63ace06016f4db8 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.