Triple
T16117053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National road 6 (Poland) |
E391029
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Goleniów |
—
|
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: Goleniów | Statement: [National road 6 (Poland), connectsCity, Goleniów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goleniów Context triple: [National road 6 (Poland), connectsCity, Goleniów]
-
A.
Goleniów
chosen
Goleniów is a town in northwestern Poland that serves as a local transport hub and gateway to the nearby regional capital Szczecin.
-
B.
Goleszów
Goleszów is a village in southern Poland that serves as the seat of Gmina Goleszów in the Silesian Voivodeship.
-
C.
Grochowe
Grochowe is a village in southeastern Poland located within the administrative district of Gmina Tuszów Narodowy in the Subcarpathian region.
-
D.
Wolyniec
Wolyniec is a Polish-origin surname most notably associated with American soccer player and coach John Wolyniec.
-
E.
Grochów
Grochów is a historic residential district in the Praga-Południe area of Warsaw, Poland, known for its pre-war architecture and role in the city’s industrial and working-class heritage.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016b5c948190b0f1eccb97ee85cc |
completed | April 17, 2026, 9:46 a.m. |
Created at: April 10, 2026, 5 a.m.