Triple

T27245954
Position Surface form Disambiguated ID Type / Status
Subject MFK Karviná E687343 entity
Predicate hasHomeDerbyOpponent P178277 FINISHED
Object FC Baník Ostrava 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: FC Baník Ostrava | Statement: [MFK Karviná, hasHomeDerbyOpponent, FC Baník Ostrava]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHomeDerbyOpponent
Context triple: [MFK Karviná, hasHomeDerbyOpponent, FC Baník Ostrava]
  • A. hasHomeDerbyFor
    Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
  • B. hasHomeStadiumInRivalry
    Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
  • C. playsHomeGamesOn
    Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
  • D. homeFieldForALTeam
    Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
  • E. hasLocalRivalryVenueWith
    Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
  • 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_69ef355547408190b5ca0d777c65040a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
PDg Predicate description generation batch_69f70e854b9c8190a3416e2189e17742 completed May 3, 2026, 8:59 a.m.
Created at: April 27, 2026, 10:41 a.m.