Triple
T18264861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 汉江 |
E437456
|
entity |
| Predicate | 河口位置 |
P4359
|
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.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
B.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
mouthOfTheWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water.
-
E.
locatedBetweenRivers
Indicates that something is situated in the area or region bounded or flanked by two rivers.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff79851481909a4bbeb14fb00647 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.