Triple
T30803711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian government of Engelbert Dollfuss |
E784439
|
entity |
| Predicate | leaderAssassinationDate |
P4179
|
FINISHED |
| Object | 25 July 1934 |
—
|
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: 25 July 1934 | Statement: [Austrian government of Engelbert Dollfuss, leaderAssassinationDate, 25 July 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderAssassinationDate Context triple: [Austrian government of Engelbert Dollfuss, leaderAssassinationDate, 25 July 1934]
-
A.
leaderAssassinated
Indicates that a leader has been killed through an intentional, targeted act of assassination.
-
B.
assassinationDate
chosen
Indicates the date on which an assassination of the referenced entity occurred.
-
C.
relatedAssassination
Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another entity.
-
D.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
E.
assassinationOrganizedBy
Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 8:42 p.m.