Triple
T21469553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdańsk County |
E529687
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Pruszcz Gdański |
—
|
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: Pruszcz Gdański | Statement: [Gdańsk County, containsTown, Pruszcz Gdański]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pruszcz Gdański Context triple: [Gdańsk County, containsTown, Pruszcz Gdański]
-
A.
Pruszcz Gdański
chosen
Pruszcz Gdański is a town in northern Poland near Gdańsk, known as a local industrial and transport hub within the Pomeranian Voivodeship.
-
B.
Wrzeszcz
Wrzeszcz is a central district of Gdańsk, Poland, known as a major residential, commercial, and transport hub of the city.
-
C.
Gryfice
Gryfice is a historic town in northwestern Poland known for its medieval urban layout and remnants of defensive walls.
-
D.
Gdynia
Gdynia is a major seaport city on Poland’s Baltic coast, developed rapidly in the 20th century into one of the country’s key maritime and economic centers.
-
E.
Starogard Gdański
Starogard Gdański is a historic town in northern Poland that serves as an important local industrial and cultural center in the Kociewie region.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea12d9048190bf51ca3efc435a64 |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:16 p.m.