Triple
T1852954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuyavia |
E41636
|
entity |
| Predicate | historicalCapital |
P2536
|
FINISHED |
| Object | Inowrocław |
E359478
|
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: Inowrocław | Statement: [Kuyavia, historicalCapital, Inowrocław]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inowrocław Context triple: [Kuyavia, historicalCapital, Inowrocław]
-
A.
Inowrocław
chosen
Inowrocław is a historic spa and industrial city in north-central Poland, known for its saltworks and location in the Kuyavia region.
-
B.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
C.
Kociewie
Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
-
D.
Jaworzno
Jaworzno is a city in southern Poland, located in the Silesian Voivodeship and known for its industrial heritage and role in the Upper Silesian urban area.
-
E.
Ostrołęka
Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb06999f4819086386aafb789a368 |
completed | March 7, 2026, 4:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b37e38ff2881909490b7b20deb149b |
completed | March 13, 2026, 3:02 a.m. |
Created at: March 4, 2026, 7:33 p.m.