Triple
T15183624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hồng Hà |
E362810
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Lô River |
E1148259
|
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: Lô River | Statement: [Hồng Hà, hasTributary, Lô River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lô River Context triple: [Hồng Hà, hasTributary, Lô River]
-
A.
Lô River
chosen
The Lô River is a significant river in northern Vietnam that flows through several provinces before joining the Red River system.
-
B.
Tuo River
The Tuo River is a significant river in Sichuan Province, China, flowing through the Chengdu region and serving as an important tributary of the upper Yangtze River.
-
C.
Lừ River
Lừ River is an urban waterway flowing through Hanoi, Vietnam, forming part of the city’s drainage and hydrological system.
-
D.
Hieu River
Hieu River is a tributary waterway in Vietnam that feeds into the larger Ca River system.
-
E.
Indong River
The Indong River is a watercourse in the Dooars region of West Bengal, India, that flows through and supports the ecosystem of Gorumara National Park.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006674c088190ba635a78c30f5637 |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b35c5488190a22195578c6da855 |
completed | May 9, 2026, 10:23 a.m. |
Created at: April 10, 2026, 3:09 a.m.