Triple
T12977673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olza River |
E321570
|
entity |
| Predicate | knownAs |
P39
|
FINISHED |
| Object | Olše |
E785944
|
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: Olše | Statement: [Olza River, knownAs, Olše]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olše Context triple: [Olza River, knownAs, Olše]
-
A.
Olše
chosen
Olše is a river in the eastern Czech Republic that flows through the Moravian-Silesian Region before joining the Oder.
-
B.
Olesno
Olesno is a historic town in southern Poland known for its medieval origins and traditional Silesian character.
-
C.
Olecko
Olecko is a small town in northeastern Poland known for its lakeside setting and location within the historic region of Masuria.
-
D.
Chełmek
Chełmek is a small town in southern Poland known historically for its shoe industry and its location near Oświęcim (Auschwitz).
-
E.
Załęski
Załęski is a Polish surname, a diacritic variant of Zaleski, borne by individuals and families of Polish origin.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8f0315c8190aae5908ba65d5867 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:38 p.m.