Triple
T21182381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | south-central Poland |
E521983
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | city of Końskie |
—
|
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: city of Końskie | Statement: [south-central Poland, contains, city of Końskie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Końskie Context triple: [south-central Poland, contains, city of Końskie]
-
A.
Kościan
Kościan is a historic town in west-central Poland, located in the Greater Poland region south of Poznań.
-
B.
Kędzierzyn-Koźle
Kędzierzyn-Koźle is a town in southern Poland known as an important industrial and river port center on the Oder River.
-
C.
Kozienice
Kozienice is a town in east-central Poland known for its large coal-fired power plant and proximity to the Kozienice Landscape Park.
-
D.
Końskie
chosen
Końskie is a town in south-central Poland known historically as a local industrial and administrative center.
-
E.
Kociewie
Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:04 p.m.