Triple
T30155462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 相关国际河流比较 |
P168501
|
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.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
B.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
-
C.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
D.
transboundaryWaterInfrastructureBetween
Indicates the existence of water-related infrastructure (such as dams, canals, or pipelines) that spans or jointly serves two or more different territorial or jurisdictional areas.
-
E.
watercourseIDCountry
Indicates that a specific watercourse is associated with, located in, or flows through a particular country.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.