Triple
T11325508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganzhou |
E268203
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Gong River |
E823070
|
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: Gong River | Statement: [Ganzhou, locatedOnRiver, Gong River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gong River Context triple: [Ganzhou, locatedOnRiver, Gong River]
-
A.
Gong River
chosen
The Gong River is a significant river in southern China that serves as a major tributary contributing to the flow of the Gan River system.
-
B.
Yi River
The Yi River is a significant river in Shandong Province, China, known for flowing through the city of Linyi and its surrounding agricultural and historical regions.
-
C.
Seoktan River
The Seoktan River is a tributary waterway in the Korean Peninsula that feeds into the larger Imjin River system.
-
D.
Louhajang River
The Louhajang River is a regional waterway in central Bangladesh that flows through Tangail District and supports local agriculture, fisheries, and transportation.
-
E.
Yeong River
The Yeong River is a river in South Korea that feeds into the larger Nakdong River system.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58b4ec4ac81908d51e3815a054704 |
completed | April 20, 2026, 2:11 a.m. |
Created at: April 8, 2026, 9:32 p.m.