Triple
T30155418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 下游起点 |
P5956
|
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.
上游所属流域
Indicates that a given upstream section of a river belongs to or is part of a particular drainage basin or watershed.
-
B.
downstreamFrom
chosen
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
C.
situatedUpstreamOf
Indicates that one entity is located in the direction from which a flow (such as water, traffic, or a process stream) originates relative to another entity along the same path or system.
-
D.
upstreamRiver
Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
-
E.
waterwayDestination
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
- 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.