Triple
T14180371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rybnik |
E351435
|
entity |
| Predicate | hasRailwayConnectionTo |
P3791
|
FINISHED |
| Object | Gliwice |
—
|
NE NERFINISHED |
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: Gliwice | Statement: [Rybnik, hasRailwayConnectionTo, Gliwice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gliwice Context triple: [Rybnik, hasRailwayConnectionTo, Gliwice]
-
A.
Gliwice
chosen
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.
-
B.
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.
-
C.
Katowice
Katowice is a major industrial and cultural city in southern Poland, known as the capital of the Silesian region.
-
D.
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.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61ca3ad88190944850c97760dcbf |
completed | April 14, 2026, 3:48 p.m. |
Created at: April 10, 2026, 1:02 a.m.