Triple
T9010358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ust-Luga |
E215452
|
entity |
| Predicate | locatedAtMouthOf |
P165
|
FINISHED |
| Object | Luga River |
E263361
|
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: Luga River | Statement: [Ust-Luga, locatedAtMouthOf, Luga River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luga River Context triple: [Ust-Luga, locatedAtMouthOf, Luga River]
-
A.
Luga River
chosen
The Luga River is a significant waterway in northwestern Russia that flows through Novgorod and Leningrad Oblasts before emptying into the Gulf of Finland in the Baltic Sea.
-
B.
Liakhvi River
The Liakhvi River is a river in central Georgia that flows through the city of Gori before joining the Kura (Mtkvari) River.
-
C.
Uzlyanka River
The Uzlyanka River is a smaller watercourse in Belarus that serves as one of the tributaries feeding into the Berezina River system.
-
D.
Zusha River
The Zusha River is a significant waterway in western Russia that feeds into the Oka River and contributes to its drainage basin.
-
E.
Tvertsa River
The Tvertsa River is a waterway in western Russia that flows through Tver Oblast and serves as a tributary of the Volga 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c1571881908d0b144786b5ee1f |
completed | April 1, 2026, 12:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14bb716cc819096a1e02e61db2e69 |
completed | April 4, 2026, 5:34 p.m. |
Created at: March 30, 2026, 7:06 p.m.