Triple

T9536641
Position Surface form Disambiguated ID Type / Status
Subject Jagiellonia Białystok E230033 entity
Predicate hasWon P2624 FINISHED
Object Polish Cup E320389 NE 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: Polish Cup | Statement: [Jagiellonia Białystok, hasWon, Polish Cup]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Polish Cup
Context triple: [Jagiellonia Białystok, hasWon, Polish Cup]
  • A. Polish Cup chosen
    The Polish Cup is Poland's premier national football knockout tournament, contested annually by clubs from various levels of the country's league system.
  • B. Polish SuperCup
    The Polish SuperCup is an annual football match in Poland contested between the winners of the national league and the Polish Cup to open the domestic season.
  • C. Ekstraklasa
    Ekstraklasa is the top professional football league in Poland, featuring the country’s highest-level clubs.
  • D. Łó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ź.
  • E. Tricity Derby
    Tricity Derby is a fiercely contested Polish football rivalry match between clubs from the Tricity metropolitan area on the Baltic coast.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98ce884c8190a8b3c2dc7c73c2c9 completed April 1, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69d14c4f1fc08190a1ad3d862717eef3 completed April 4, 2026, 5:37 p.m.
Created at: March 30, 2026, 8:01 p.m.