Triple
T1417974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Christoph von Königsmarck |
E31961
|
entity |
| Predicate | allegedMannerOfDeath |
P27547
|
FINISHED |
| Object | murder |
—
|
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 | Statement: [Philip Christoph von Königsmarck, allegedMannerOfDeath, murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedMannerOfDeath Context triple: [Philip Christoph von Königsmarck, allegedMannerOfDeath, murder]
-
A.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
diedInCustodyOf
Indicates that an individual died while under the control, supervision, or physical custody of a specified authority or entity.
-
C.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
D.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
E.
placeOfDeath
Indicates the location where an entity (typically a person or animal) died.
- F. None of above. chosen
Provenance (4 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c404e92c8190bd018673383f4534 |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:59 p.m.