Triple
T4702435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bytom |
E104306
|
entity |
| Predicate | locatedNear |
P294
|
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: [Bytom, locatedNear, Chorzów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chorzów Context triple: [Bytom, locatedNear, 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.
Sosnowiec
Sosnowiec is an industrial city in southern Poland, located in the Silesian Voivodeship and known as part of the Upper Silesian metropolitan area.
-
D.
Tychy
Tychy is a city in the Silesian region of southern Poland, known for its brewing industry and role as a planned industrial center.
-
E.
Dąbrowa Górnicza
Dąbrowa Górnicza is an industrial city in southern Poland’s Silesian Voivodeship, known for its heavy industry, mining heritage, and proximity to the unique Błędów Desert.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd63cec7988190b5f1d04d4f95314a |
completed | March 20, 2026, 3:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9742fd0dc8190a154cf83c87eb508 |
completed | March 29, 2026, 6:49 p.m. |
Created at: March 20, 2026, 1:17 p.m.