Triple
T9869239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharkiv River |
E239912
|
entity |
| Predicate | mouthOf |
P1008
|
FINISHED |
| Object | Lopan River |
E282739
|
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: Lopan River | Statement: [Kharkiv River, mouthOf, Lopan River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lopan River Context triple: [Kharkiv River, mouthOf, Lopan River]
-
A.
Lopan River
chosen
The Lopan River is a waterway in northeastern Ukraine that flows through the city of Kharkiv and forms part of its urban landscape and drainage system.
-
B.
Uono River
The Uono River is a river in Niigata Prefecture, Japan, that flows through the Uonuma region before joining the Shinano River.
-
C.
Tuul River
The Tuul River is a major river in central Mongolia that flows through the capital city, Ulaanbaatar, and plays an important role in the region’s ecology and water supply.
-
D.
Limmat River
The Limmat River is a major Swiss waterway that flows out of Lake Zurich and runs through the city of Zurich before joining the Aare River.
-
E.
Porsuk River
The Porsuk River is a significant waterway in western Turkey that flows through the city of Eskişehir before joining the Sakarya River.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d498b481908f82f31f98b57c7e |
completed | April 2, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20d60b2f8819087f4242f36b05a49 |
completed | April 5, 2026, 7:21 a.m. |
Created at: March 30, 2026, 8:36 p.m.