Triple
T12235999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kociewie |
E291592
|
entity |
| Predicate | crossedByRiver |
P225
|
FINISHED |
| Object | Wierzyca River |
E1222181
|
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: Wierzyca River | Statement: [Kociewie, crossedByRiver, Wierzyca River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wierzyca River Context triple: [Kociewie, crossedByRiver, Wierzyca River]
-
A.
Wierzyca River
chosen
The Wierzyca River is a river in northern Poland that flows through the Pomeranian region, including the town of Starogard Gdański, before joining the Vistula.
-
B.
Miedzianka River
The Miedzianka River is a small river in southwestern Poland that flows through the town of Bogatynia near the Czech and German borders.
-
C.
Mleczna River
The Mleczna River is a small river in central Poland that flows through the city of Radom and forms part of its local water system.
-
D.
Wieprz River
The Wieprz River is a major river in eastern Poland that flows through the Lublin region before joining the Vistula River.
-
E.
Kacza River
The Kacza River is a small river in northern Poland that flows through the Gdynia district of Mały Kack into the Baltic Sea.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb2892c81909a97b3ad6ec2c21b |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a4fffa7c81909bcc833b44ddf66f |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 8, 2026, 9:51 p.m.