Triple
T12726487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarocin |
E304120
|
entity |
| Predicate | hasRailConnectionTo |
P848
|
FINISHED |
| Object | Krotoszyn |
E492478
|
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: Krotoszyn | Statement: [Jarocin, hasRailConnectionTo, Krotoszyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krotoszyn Context triple: [Jarocin, hasRailConnectionTo, Krotoszyn]
-
A.
Krotoszyn
chosen
Krotoszyn is a historic town in west-central Poland known for its medieval origins and changing political affiliations, including periods under Prussian and German rule.
-
B.
Kruszwica
Kruszwica is a historic town in central Poland, known for its medieval Mouse Tower, lakeside setting on Lake Gopło, and role as an early center of Polish statehood.
-
C.
Kraśnik
Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
-
D.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
-
E.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96415ebe48190ae935bc3a9b00f65 |
completed | April 10, 2026, 8:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fb168548190afb975ef60fa5f3e |
completed | May 11, 2026, 4:48 a.m. |
Created at: April 9, 2026, 5:25 p.m.