Triple
T11801419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leshan |
E280634
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Qingyi River |
E649825
|
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: Qingyi River | Statement: [Leshan, locatedOnRiver, Qingyi River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qingyi River Context triple: [Leshan, locatedOnRiver, Qingyi River]
-
A.
Qingyi River
chosen
The Qingyi River is a significant river in southwestern China that flows through Sichuan Province and contributes to the Min River system within the upper Yangtze basin.
-
B.
Xiaoqing River
The Xiaoqing River is a significant river in Shandong Province, China, flowing through the city of Jinan and serving as an important regional waterway.
-
C.
Xiliao River
The Xiliao River is a major river in northeastern China that forms part of the upper Liao River system and drains a large area of Inner Mongolia and Liaoning.
-
D.
Qingshui River
Qingshui River is a river in Xinjiang, China, that serves as a major tributary feeding water into Bosten Lake.
-
E.
Qingshui River
The Qingshui River is a tributary waterway in China that feeds into the larger Yuan 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a4512c8190b7782e1dee053000 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f41775f4348190a82e8f6c265c9c36 |
completed | May 1, 2026, 3:01 a.m. |
Created at: April 8, 2026, 9:42 p.m.