Triple

T21337408
Position Surface form Disambiguated ID Type / Status
Subject Tychy E526085 entity
Predicate hasSportsClub P346 FINISHED
Object GKS Tychy 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: GKS Tychy | Statement: [Tychy, hasSportsClub, GKS Tychy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GKS Tychy
Context triple: [Tychy, hasSportsClub, GKS Tychy]
  • A. GKS Tychy chosen
    GKS Tychy is a Polish multi-sports club best known for its professional football and ice hockey teams based in the city of Tychy.
  • B. GKS Katowice
    GKS Katowice is a Polish multi-sports club from the city of Katowice, best known for its football and ice hockey teams competing in national leagues.
  • C. KS Ruch Chorzów
    KS Ruch Chorzów is a historic Polish football club from Chorzów, renowned as one of the country’s most successful and traditional teams.
  • D. Raków Częstochowa
    Raków Częstochowa is a Polish professional football club based in Częstochowa, known for its recent rise to prominence in the country’s top division.
  • E. GKS Jastrzębie
    GKS Jastrzębie is a Polish football club based in Jastrzębie-Zdrój, known for competing in the national league system and representing the Silesian region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51c33048190ab27cede74ef798c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e898da015081909e83fb62cf166b9a completed April 22, 2026, 9:46 a.m.
Created at: April 16, 2026, 4:43 p.m.