Triple
T4907830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mže |
E109954
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Úterský potok |
E478499
|
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: Úterský potok | Statement: [Mže, hasTributary, Úterský potok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Úterský potok Context triple: [Mže, hasTributary, Úterský potok]
-
A.
Zlínský potok
Zlínský potok is a small stream in the Czech Republic that flows through and gives its name to the city of Zlín.
-
B.
Hamerský potok
chosen
Hamerský potok is a small stream in the Czech Republic that serves as one of the tributaries of the Mže River.
-
C.
Huczwa River
The Huczwa River is a tributary watercourse in eastern Poland that feeds into the Bug River and contributes to the region’s drainage system.
-
D.
Bystřice River
The Bystřice River is a watercourse in the Czech Republic that flows through the historic mining town of Jáchymov in the Ore Mountains region.
-
E.
Krzna River
The Krzna River is a significant river in eastern Poland that serves as one of the main tributaries of the Bug River, flowing through the Lublin region.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e7452d481909078a0027e2a4566 |
completed | March 20, 2026, 3:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be779ed15481908366b5e22c9960e6 |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:29 p.m.