Triple
T3330357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilkenau |
E70017
|
entity |
| Predicate | correspondsTo |
P6530
|
FINISHED |
| Object | Polish name "Olkusz" |
E12746
|
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: Polish name "Olkusz" | Statement: [Ilkenau, correspondsTo, Polish name "Olkusz"]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polish name "Olkusz" Context triple: [Ilkenau, correspondsTo, Polish name "Olkusz"]
-
A.
Olkusz
chosen
Olkusz is a historic town in southern Poland known for its medieval silver and lead mining heritage and well-preserved Old Town.
-
B.
Olkusz urban area
Olkusz urban area is the built-up and administratively organized urban region centered on the town of Olkusz in southern Poland.
-
C.
Oleśnica
Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
-
D.
Olecko
Olecko is a small town in northeastern Poland known for its lakeside setting and location within the historic region of Masuria.
-
E.
Gietrzwałd
Gietrzwałd is a village in northern Poland known as a Catholic pilgrimage site due to reported Marian apparitions in 1877.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a810e2c8190bfc206bdeb1ac5b8 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.