Triple
T16480394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kander river basin |
E400300
|
entity |
| Predicate | hasElevationZone |
P73807
|
FINISHED |
| Object | high alpine |
—
|
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: high alpine | Statement: [Kander river basin, hasElevationZone, high alpine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationZone Context triple: [Kander river basin, hasElevationZone, high alpine]
-
A.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
B.
hasHigherElevationArea
Indicates that one area is situated at a greater elevation above sea level than another area.
-
C.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
D.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
E.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01f6c88190b75a0d6c94786426 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.