Triple
T15183574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sông Hồng |
E362809
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Sông Lô |
E1146231
|
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: Sông Lô | Statement: [Sông Hồng, hasTributary, Sông Lô]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sông Lô Context triple: [Sông Hồng, hasTributary, Sông Lô]
-
A.
Sông Lô
chosen
Sông Lô is a river in northern Vietnam known for its historical significance and scenic landscapes as part of the Lô River system.
-
B.
Hoang Long River
Hoang Long River is a river in northern Vietnam that flows through Ninh Binh Province, contributing to the region’s agriculture and landscape.
-
C.
Thi Tinh River
Thi Tinh River is a tributary waterway in southern Vietnam that feeds into the Saigon River and supports the surrounding agricultural and local communities.
-
D.
Luong River
Luong River is a tributary waterway in Vietnam that feeds into the larger Ma River system.
-
E.
Sông Ninh Cơ
Sông Ninh Cơ is a river in northern Vietnam that flows through Nam Định Province and serves as an important waterway for transportation and irrigation.
- 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_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01dc23d081908ad6985bae5741ce |
completed | May 9, 2026, 9:43 a.m. |
Created at: April 10, 2026, 3:09 a.m.