Triple
T29244880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaoligong Mountain |
E741412
|
entity |
| Predicate | riverBetween |
P23609
|
FINISHED |
| Object | Nujiang (Salween) River to the east |
—
|
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: Nujiang (Salween) River to the east | Statement: [Gaoligong Mountain, riverBetween, Nujiang (Salween) River to the east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBetween Context triple: [Gaoligong Mountain, riverBetween, Nujiang (Salween) River to the east]
-
A.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
B.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
C.
locatedBetweenRivers
chosen
Indicates that something is situated in the area or region bounded or flanked by two rivers.
-
D.
riverRelation
Indicates a spatial or geographic relationship between one river and another, such as confluence, branching, or relative positioning.
-
E.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 12:32 p.m.