Triple
T10296838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorzów |
E241511
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Świętochłowice |
E773834
|
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: Świętochłowice | Statement: [Chorzów, hasNeighbour, Świętochłowice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Świętochłowice Context triple: [Chorzów, hasNeighbour, Świętochłowice]
-
A.
Świętochłowice
chosen
Świętochłowice is an industrial city in southern Poland, located in the Upper Silesian metropolitan area.
-
B.
Wodzisław Śląski
Wodzisław Śląski is a town in southern Poland known for its historic urban core and location in the industrial and mining region of Upper Silesia.
-
C.
Chorzów
Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
-
D.
Polkowice
Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
-
E.
Włoszczowa
Włoszczowa is a town in south-central Poland known as the seat of Włoszczowa County and a local administrative and service center.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ebd258819099fadddcd13099fc |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68e99c2608190b923ca8a9178fea2 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 6, 2026, 11:43 a.m.