Triple
T31278763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwine Dollfuss |
E797602
|
entity |
| Predicate | spouseAssassinated |
P192994
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alwine Dollfuss, spouseAssassinated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseAssassinated Context triple: [Alwine Dollfuss, spouseAssassinated, yes]
-
A.
spouseExecuted
Indicates that one person’s spouse was put to death, typically as a result of a legal or extrajudicial execution.
-
B.
spouseExecutedFor
Indicates that one person’s spouse was put to death, typically as a result of a legal or punitive execution.
-
C.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
D.
spouseExecutionMethod
Indicates the method by which a person's spouse was executed.
-
E.
assassinated
Indicates that one entity deliberately killed another, typically for political, ideological, or strategic reasons.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: April 29, 2026, 9:13 p.m.