Triple
T16788287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokmok |
E408035
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Chu River |
E93176
|
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: Chu River | Statement: [Tokmok, locatedOnRiver, Chu River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chu River Context triple: [Tokmok, locatedOnRiver, Chu River]
-
A.
Chu River
The Chu River is a waterway that serves as a tributary within the Ma River basin in Southeast Asia.
-
B.
Chu River
chosen
The Chu River is a major river in Central Asia that flows through Kyrgyzstan and Kazakhstan, playing an important role in regional agriculture and water supply.
-
C.
Kuang River
The Kuang River is a tributary waterway in northern Thailand that feeds into the Ping River, contributing to the Chao Phraya River basin.
-
D.
Lian River
The Lian River is a significant river in southern China that serves as a major tributary within the Xiang River system, contributing to the hydrology of the broader Yangtze River basin.
-
E.
Xin River
The Xin River is a major river in Jiangxi Province, China, that serves as one of the principal tributaries supplying water to Poyang Lake.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21c49788190b9a2ca2101604f64 |
completed | April 18, 2026, 4:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab09932c8190ba16a349c4938c16 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.