Triple
T30155562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江武汉段 |
E766509
|
entity |
| Predicate | 所在流域 |
P72732
|
FINISHED |
| Object | 长江流域 |
—
|
LITERAL 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: 长江流域 | Statement: [长江武汉段, 所在流域, 长江流域]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在流域 Context triple: [长江武汉段, 所在流域, 长江流域]
-
A.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
B.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
C.
associatedRiverBasin
chosen
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.