Triple

T17396624
Position Surface form Disambiguated ID Type / Status
Subject Lechia Gdańsk E422970 entity
Predicate rivalry P903 FINISHED
Object Tricity Derby 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: Tricity Derby | Statement: [Lechia Gdańsk, rivalry, Tricity Derby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tricity Derby
Context triple: [Lechia Gdańsk, rivalry, Tricity Derby]
  • A. Tricity Derby chosen
    Tricity Derby is a fiercely contested Polish football rivalry match between clubs from the Tricity metropolitan area on the Baltic coast.
  • B. Łódź derby
    The Łódź derby is the fiercely contested football rivalry between the two major clubs from the Polish city of Łódź, Widzew Łódź and ŁKS Łódź.
  • C. Kraków derby
    The Kraków derby is the fiercely contested football rivalry between Kraków’s two major clubs, Wisła Kraków and Cracovia, and is one of the oldest and most intense derbies in Poland.
  • D. Silesian derby
    The Silesian derby is a fiercely contested football rivalry match between major clubs from Poland’s Silesia region, most prominently Górnik Zabrze and their local adversaries.
  • E. Derby Trójmiasta
    Derby Trójmiasta is a Polish football rivalry match between clubs from the Tricity metropolitan area of Gdańsk, Gdynia, and Sopot.
  • 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43abd9b748190bd55c863276d9e3a completed April 19, 2026, 2:15 a.m.
Created at: April 10, 2026, 5:45 a.m.