Triple

T30181493
Position Surface form Disambiguated ID Type / Status
Subject Swiss Vice-Consul in Budapest E767211 entity
Predicate riskIncurred P59284 FINISHED
Object defiance of Nazi and allied authorities 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: defiance of Nazi and allied authorities | Statement: [Swiss Vice-Consul in Budapest, riskIncurred, defiance of Nazi and allied authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riskIncurred
Context triple: [Swiss Vice-Consul in Budapest, riskIncurred, defiance of Nazi and allied authorities]
  • A. riskTaken chosen
    Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
  • B. riskElement
    Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
  • C. riskTakenFor
    Indicates that one entity accepts or undertakes a risk for the benefit, protection, or sake of another entity.
  • D. riskCoverage
    Indicates the extent to which a particular risk is protected against, mitigated, or compensated for by a policy, measure, or arrangement.
  • E. riskType
    Indicates the category or nature of risk associated with an entity, event, or relationship.
  • 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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67f419e088190ba19a6ab9465d951 completed May 2, 2026, 10:48 p.m.
PD Predicate disambiguation batch_69f673c7a4588190837854f3ef61e6bf completed May 2, 2026, 9:59 p.m.
Created at: April 29, 2026, 7:26 p.m.