Triple
T9203957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khatanga River |
E220921
|
entity |
| Predicate | hasSettlementOnBank |
P1010
|
FINISHED |
| Object | Khatanga |
E786775
|
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: Khatanga | Statement: [Khatanga River, hasSettlementOnBank, Khatanga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khatanga Context triple: [Khatanga River, hasSettlementOnBank, Khatanga]
-
A.
Khatanga
chosen
Khatanga is a remote Arctic port settlement in northern Siberia, Russia, serving as a key access point to the Laptev Sea and surrounding tundra regions.
-
B.
Khatanga River
The Khatanga River is a major river in northern Siberia that flows through the Krasnoyarsk Krai region of Russia before emptying into the Arctic Ocean.
-
C.
Yelshanka
Yelshanka is a locality in Russia best known as the namesake of Yelshanka railway station.
-
D.
Yakut
Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
-
E.
Yura
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd944e6208190adfcc7f75197387d |
completed | April 1, 2026, 8:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09b96f0e88190bd80594fe3f769b8 |
completed | April 4, 2026, 5:03 a.m. |
Created at: March 30, 2026, 7:26 p.m.