Triple
T12989098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doetinchem |
E321848
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Gorzów Wielkopolski |
—
|
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: Gorzów Wielkopolski | Statement: [Doetinchem, twinTown, Gorzów Wielkopolski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gorzów Wielkopolski Context triple: [Doetinchem, twinTown, Gorzów Wielkopolski]
-
A.
Gorzów Wielkopolski
chosen
Gorzów Wielkopolski is a city in western Poland, known as one of the two capitals of the Lubusz Voivodeship and an important regional industrial and cultural center.
-
B.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
C.
Grudziądz
Grudziądz is a historic city in northern Poland on the Vistula River, known for its medieval granaries and well-preserved Old Town.
-
D.
Gorzów Śląski
Gorzów Śląski is a small town in southwestern Poland known for its location in the historical region of Upper Silesia.
-
E.
Inowrocław
Inowrocław is a historic spa and industrial city in north-central Poland, known for its saltworks and location in the Kuyavia 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e75b9f88190a54372c2a1223a4e |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:42 p.m.