Triple
T18735770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivangorod |
E458157
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Narva 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: Narva River | Statement: [Ivangorod, locatedOnRiver, Narva River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Narva River Context triple: [Ivangorod, locatedOnRiver, Narva River]
-
A.
Narva River
chosen
The Narva River is a major river in northeastern Europe that forms part of the border between Estonia and Russia, flowing from Lake Peipus into the Baltic Sea.
-
B.
Daugava River
The Daugava River is a major Eastern European river flowing through Russia, Belarus, and Latvia before emptying into the Baltic Sea.
-
C.
Lida River
The Lida River is a waterway in western Belarus that flows through the town of Lida and forms part of the region’s local river system.
-
D.
Gołdapa River
The Gołdapa River is a watercourse in northeastern Poland that flows through the town of Gołdap before joining larger regional river systems.
-
E.
Onega River
The Onega River is a major river in northwestern Russia that flows through the Karelia region before emptying into the White 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d7ae10081908bc6857d1d147eef |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.