Triple
T12729311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cieszyn |
E304189
|
entity |
| Predicate | hasBorderRiver |
P225
|
FINISHED |
| Object | Olza River |
—
|
NE NERFINISHED |
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: Olza River | Statement: [Cieszyn, hasBorderRiver, Olza River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olza River Context triple: [Cieszyn, hasBorderRiver, Olza River]
-
A.
Olza River
chosen
The Olza River is a Central European river that flows through the historical region of Cieszyn Silesia, forming part of the border between Poland and the Czech Republic.
-
B.
Osława River
The Osława River is a river in southeastern Poland that flows through the Carpathian region before joining the San River.
-
C.
Pagladia River
Pagladia River is a tributary watercourse in northeastern India that feeds into the Manas River within the Brahmaputra river system.
-
D.
Ozerna River
The Ozerna River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the Ruza River within the Moscow region’s river system.
-
E.
Sestra River
The Sestra River is a watercourse in northwestern Russia that flows into the eastern part of the Gulf of Finland in the Baltic Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d964172490819080cd022ff8290b6e |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.