Triple
T30031156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 博斯腾湖 |
E763020
|
entity |
| Predicate | 主要补给河流 |
P57854
|
FINISHED |
| Object | 开都河 |
—
|
NE NERFINISHED |
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: 开都河 | Statement: [博斯腾湖, 主要补给河流, 开都河]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 主要补给河流 Context triple: [博斯腾湖, 主要补给河流, 开都河]
-
A.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
B.
isMajorWatercourseOf
chosen
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
C.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
-
D.
majorRiverRole
Indicates that a river plays a primary or dominant role in a specified context, such as geography, economy, culture, or ecology, relative to other rivers in the area.
-
E.
上游所属流域
Indicates that a given upstream section of a river belongs to or is part of a particular drainage basin or watershed.
- F. None of above.
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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679afd2a88190856acb9e2d1f87d3 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:50 p.m.