Triple

T26637408
Position Surface form Disambiguated ID Type / Status
Subject Albanian Cup E668676 entity
Predicate knockoutRule P40473 FINISHED
Object single-elimination ties in most rounds 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: single-elimination ties in most rounds | Statement: [Albanian Cup, knockoutRule, single-elimination ties in most rounds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knockoutRule
Context triple: [Albanian Cup, knockoutRule, single-elimination ties in most rounds]
  • A. hasKnockoutRule chosen
    Indicates that a rule or condition exists specifying when and how a knockout (elimination) occurs in a competitive or game-like setting.
  • B. isKnockout
    Indicates that one entity defeats or eliminates another in a decisive, often single-step outcome, leaving the latter unable to continue.
  • C. knockoutNature
    Indicates that one entity causes another to be eliminated, disabled, or rendered nonfunctional, typically in a decisive or forceful manner.
  • D. validationRule
    Indicates that a specified condition or constraint must be satisfied to consider a related entity, input, or operation valid.
  • E. keyRule
    Indicates that a rule or principle functions as a key or primary governing condition for something.
  • 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_69ee9d0024b8819090a7c8cf669a3b6c completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6162d48f88190b43087b02cbf30e8 completed May 2, 2026, 3:20 p.m.
PD Predicate disambiguation batch_69f60b8bb0d08190ab5a9a2a8847c6f4 completed May 2, 2026, 2:34 p.m.
Created at: April 27, 2026, 2:27 a.m.