Triple
T18321093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobol River |
E438879
|
entity |
| Predicate | hasCityOnBank |
P7935
|
FINISHED |
| Object | Rudny |
—
|
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: Rudny | Statement: [Tobol River, hasCityOnBank, Rudny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rudny Context triple: [Tobol River, hasCityOnBank, Rudny]
-
A.
Rudny
chosen
Rudny is an industrial city in northern Kazakhstan known for its mining activities, particularly iron ore extraction.
-
B.
Rospuda River
The Rospuda River is a scenic waterway in northeastern Poland known for its unspoiled natural landscapes and ecologically valuable wetlands.
-
C.
Sokołówka River
The Sokołówka River is a small urban watercourse flowing through the city of Łódź in central Poland.
-
D.
Leśna River
The Leśna River is a watercourse in northeastern Poland and western Belarus that flows through the town of Hajnówka and the Białowieża Forest region.
-
E.
Drwęca River
The Drwęca River is a river in northern Poland that flows through the Warmian-Masurian and Kuyavian-Pomeranian regions before joining the Vistula.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
Created at: April 10, 2026, 10:36 a.m.