Triple
T7162957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argun |
E166991
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Argun River |
E110759
|
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: Argun River | Statement: [Argun, locatedOnRiver, Argun River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Argun River Context triple: [Argun, locatedOnRiver, Argun River]
-
A.
Argun River
chosen
The Argun River is a major river in Northeast Asia that forms part of the border between Russia and China and serves as one of the headwaters of the Amur River.
-
B.
Chagan River
The Chagan River is a smaller watercourse in Russia and Kazakhstan that feeds into the Ural River within the Ural basin.
-
C.
Barguzin River
The Barguzin River is a major river in eastern Siberia, Russia, that flows through the Barguzin Valley before emptying into Lake Baikal.
-
D.
Argun
Argun is a small city in the Chechen Republic of Russia, located just southeast of the regional capital Grozny.
-
E.
Tumen River
The Tumen River is a border river in Northeast Asia that flows between China, North Korea, and Russia before emptying into the Sea of Japan (East Sea).
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b4de5bc08190a569701311631bd3 |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 2:47 p.m.