Triple

T30803710
Position Surface form Disambiguated ID Type / Status
Subject Austrian government of Engelbert Dollfuss E784439 entity
Predicate leaderAssassinated P179052 FINISHED
Object Engelbert Dollfuss 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: Engelbert Dollfuss | Statement: [Austrian government of Engelbert Dollfuss, leaderAssassinated, Engelbert Dollfuss]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: leaderAssassinated
Context triple: [Austrian government of Engelbert Dollfuss, leaderAssassinated, Engelbert Dollfuss]
  • A. wasAssassinatedIn
    Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
  • B. assassinatedIn
    Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
  • C. wasAssassinationTarget
    Indicates that an entity was the intended victim or objective of an assassination attempt.
  • D. relatedAssassination
    Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another entity.
  • E. assassinationOrganizedBy
    Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
  • 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_69f224b3a7ec819096939414d103e31e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f719cc31ec819099bebcf833b14d76 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71820c6c88190ab38b4fa626d22cc completed May 3, 2026, 9:40 a.m.
PDg Predicate description generation batch_69f71995853c8190912025c0e83640c8 completed May 3, 2026, 9:47 a.m.
Created at: April 29, 2026, 8:42 p.m.