Triple
T12662821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Górnik Zabrze |
E302466
|
entity |
| Predicate | hasWon |
P2624
|
FINISHED |
| Object | Polish SuperCup |
E323652
|
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 SuperCup | Statement: [Górnik Zabrze, hasWon, Polish SuperCup]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polish SuperCup Context triple: [Górnik Zabrze, hasWon, Polish SuperCup]
-
A.
Polish SuperCup
chosen
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.
-
B.
Polish Cup
The Polish Cup is Poland's premier national football knockout tournament, contested annually by clubs from various levels of the country's league system.
-
C.
Ekstraklasa
Ekstraklasa is the top professional football league in Poland, featuring the country’s highest-level clubs.
-
D.
Tricity Derby
Tricity Derby is a fiercely contested Polish football rivalry match between clubs from the Tricity metropolitan area on the Baltic coast.
-
E.
Łó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ź.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617c5b888190b37d4ede139bb49e |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684dfce0c8190b3b8260450bd6967 |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:19 p.m.