Triple
T17224509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niepołomice |
E418076
|
entity |
| Predicate | roadAccessTo |
P22549
|
FINISHED |
| Object | Bochnia |
—
|
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: Bochnia | Statement: [Niepołomice, roadAccessTo, Bochnia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bochnia Context triple: [Niepołomice, roadAccessTo, Bochnia]
-
A.
Bochnia
chosen
Bochnia is a historic town in southern Poland best known for its medieval salt mine, one of the oldest in Europe.
-
B.
Bochorna
Bochorna is a remote highland village in the Tusheti region of northeastern Georgia, known as one of the highest permanently inhabited settlements in Europe.
-
C.
Krapkowice
Krapkowice is a small town in southwestern Poland known for its location on the Oder River and its local industry, including paper and cement production.
-
D.
Kolanowice
Kolanowice is a village located in southwestern Poland within the Opole Voivodeship.
-
E.
Trzebnica
Trzebnica is a historic town in southwestern Poland known for its medieval Cistercian abbey and religious significance.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddfe3bc8190b22cee4fc0590b74 |
completed | April 19, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:38 a.m.