Triple
T11862621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorkuta |
E282195
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Vorkuta River |
E979534
|
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: Vorkuta River | Statement: [Vorkuta, namedAfter, Vorkuta River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vorkuta River Context triple: [Vorkuta, namedAfter, Vorkuta River]
-
A.
Vorkuta River
chosen
The Vorkuta River is a waterway in the Komi Republic of Russia that flows through the Arctic city of Vorkuta and ultimately drains toward the Arctic Ocean basin.
-
B.
Vetluga River
The Vetluga River is a significant waterway in western Russia that flows through several regions before joining the Volga River.
-
C.
Sidorovskaya River
The Sidorovskaya River is a significant tributary watercourse in western Siberia that feeds into Russia’s Taz River system.
-
D.
Snezhnaya River
The Snezhnaya River is a Siberian river in Russia that serves as one of the tributaries feeding into Lake Baikal.
-
E.
Ichka River
The Ichka River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the Yauza River within the Moscow region.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6344d86648190ad270517b36c8815 |
completed | May 2, 2026, 5:28 p.m. |
Created at: April 8, 2026, 9:43 p.m.