Triple
T13137293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kursk |
E312116
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Seym 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: Seym River | Statement: [Kursk, locatedOnRiver, Seym River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seym River Context triple: [Kursk, locatedOnRiver, Seym River]
-
A.
Seym River
chosen
The Seym River is a significant Eastern European waterway that flows through parts of Russia and northeastern Ukraine, serving as an important tributary of the Desna River.
-
B.
Sakmara River
The Sakmara River is a major river in Russia that flows through the southern Ural region before joining the Ural River.
-
C.
Salmysh River
The Salmysh River is a lesser-known river in Russia that serves as a tributary within the Ural region’s extensive river network.
-
D.
Khudosey River
The Khudosey River is a significant watercourse in northern Siberia, Russia, known as one of the main tributaries contributing to the Taz River basin.
-
E.
Sestra River
The Sestra River is a watercourse in northwestern Russia that flows into the eastern part of the Gulf of Finland in the Baltic 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b53fbc8190a0f209c32a00f6cb |
completed | April 10, 2026, 11:03 p.m. |
Created at: April 9, 2026, 9:09 p.m.