Triple
T25229093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geli Raubal |
E632173
|
entity |
| Predicate | officialMannerOfDeath |
P48923
|
FINISHED |
| Object | suicide |
—
|
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: suicide | Statement: [Geli Raubal, officialMannerOfDeath, suicide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialMannerOfDeath Context triple: [Geli Raubal, officialMannerOfDeath, suicide]
-
A.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
B.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
C.
hasMannerOfDeath
chosen
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
D.
deathDetails
Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
-
E.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:04 p.m.