Triple
T12662809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Górnik Zabrze |
E302466
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Górnik |
E302466
|
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: Górnik | Statement: [Górnik Zabrze, shortName, Górnik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Górnik Context triple: [Górnik Zabrze, shortName, Górnik]
-
A.
Górnik Łęczna
Górnik Łęczna is a Polish professional football club based in Łęczna that competes in the country’s league system.
-
B.
Górnik Zabrze
chosen
Górnik Zabrze is a historic Polish football club from Zabrze, known as one of the country’s most successful and traditional teams.
-
C.
Ruda Śląska
Ruda Śląska is an industrial city in southern Poland’s Silesian Voivodeship, known for its coal mining heritage and role within the Upper Silesian urban area.
-
D.
Raków
Raków was a prominent early modern Polish town known as the intellectual and organizational hub of the Socinian (Polish Brethren) religious movement.
-
E.
Piast Gliwice
Piast Gliwice is a Polish professional football club based in the city of Gliwice that competes in the country's top league, the Ekstraklasa.
- 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_69f6688819fc8190bc03a1a11f96d25f |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:19 p.m.