Triple

T26390037
Position Surface form Disambiguated ID Type / Status
Subject Austrian Cup E663384 entity
Predicate deciderInDrawnMatches P125394 FINISHED
Object penalty shoot-out 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: penalty shoot-out | Statement: [Austrian Cup, deciderInDrawnMatches, penalty shoot-out]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deciderInDrawnMatches
Context triple: [Austrian Cup, deciderInDrawnMatches, penalty shoot-out]
  • A. decidingMethodForDrawnFinals
    Indicates the method or procedure used to determine the outcome or winner when a final match or contest ends in a draw.
  • B. deciderInKnockout chosen
    Indicates that an entity serves as the deciding factor or tiebreaker in determining the outcome of a knockout-stage contest or match.
  • C. decidingMatchFor
    Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
  • D. finalMatchDetermines
    Indicates that the outcome of a final match decides or establishes a particular result, status, or consequence for the related entities.
  • E. finalMatchDecidedBy
    Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
  • 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f62d53ad58819080c5227c7a729d15 completed May 2, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69f62c15952881908a5ea0c25904afec completed May 2, 2026, 4:53 p.m.
Created at: April 26, 2026, 11:25 p.m.