Triple
T34676071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo Bettauer |
E890496
|
entity |
| Predicate | wasMurderedBy |
P33482
|
FINISHED |
| Object | Otto Rothstock |
—
|
NE NERFINISHED |
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: Otto Rothstock | Statement: [Hugo Bettauer, wasMurderedBy, Otto Rothstock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMurderedBy Context triple: [Hugo Bettauer, wasMurderedBy, Otto Rothstock]
-
A.
murderVictimOf
chosen
Indicates that one entity is the person who was killed by another entity in an act of murder.
-
B.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
-
C.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
D.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
E.
murderedAlongWith
Indicates that one entity was killed in the same incident or event as another entity.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f723241a188190bc3e8b2236279511 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.