Triple
T1517175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katowice |
E32146
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Chorzów |
E241511
|
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: Chorzów | Statement: [Katowice, near, Chorzów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chorzów Context triple: [Katowice, near, Chorzów]
-
A.
Chorzów
chosen
Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
-
B.
Gliwice
Gliwice is a historic industrial and academic city in southern Poland’s Silesian region, known for its engineering university and the landmark Gliwice Radio Tower.
-
C.
Polkowice
Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
-
D.
Wałbrzych
Wałbrzych is a city in southwestern Poland known for its industrial heritage, historic coal mining, and proximity to the Sudetes mountains.
-
E.
Kociewie
Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a907eb7d108190bf26199744d510d7 |
completed | March 5, 2026, 4:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24a7f3c5c8190b742a45a50c74ca8 |
completed | March 12, 2026, 5:09 a.m. |
Created at: March 4, 2026, 7:26 p.m.