Triple
T5328954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarnów Voivodeship |
E123255
|
entity |
| Predicate | containedCity |
P8465
|
FINISHED |
| Object | Bochnia |
E24511
|
NE FINISHED |
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: [Tarnów Voivodeship, containedCity, Bochnia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bochnia Context triple: [Tarnów Voivodeship, containedCity, 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.
Kraśnik
Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
-
C.
Bolesławiec
Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
-
D.
Chorzów
Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
-
E.
Chrzanów
Chrzanów is a town in southern Poland known for its historical architecture and role as a local industrial and administrative center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8593bd6c8190b2054e548ddf2458 |
completed | March 20, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf18b396c08190be60bcb9ac933b5e |
completed | March 21, 2026, 10:16 p.m. |
Created at: March 20, 2026, 2 p.m.