Triple
T22721011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Fałków |
E561858
|
entity |
| Predicate | hasLocalGovernmentSeat |
P21613
|
FINISHED |
| Object | Fałkó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: Fałków | Statement: [Gmina Fałków, hasLocalGovernmentSeat, Fałków]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fałków Context triple: [Gmina Fałków, hasLocalGovernmentSeat, Fałków]
-
A.
Fałków
chosen
Fałków is a village in south-central Poland that serves as the seat of the rural administrative district called Gmina Fałków.
-
B.
Goleniów
Goleniów is a town in northwestern Poland that serves as a local transport hub and gateway to the nearby regional capital Szczecin.
-
C.
Kowary
Kowary is a small town in southwestern Poland, located in the Lower Silesian Voivodeship near the Karkonosze Mountains, known historically for mining and tourism.
-
D.
Falsztyn
Falsztyn is a small village in southern Poland, located in the Lesser Poland Voivodeship near the Slovak border.
-
E.
Sułów
Sułów is a village in eastern Poland located within Zamość County in the Lublin Voivodeship.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17911a4fc81908a125209aea77e22 |
completed | April 29, 2026, 3:20 a.m. |
Created at: April 17, 2026, 3:19 p.m.