Triple
T31785523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaksgam Valley |
E811315
|
entity |
| Predicate | nearestMajorRange |
P105906
|
FINISHED |
| Object | K2 region of Karakoram |
—
|
NE NERFINISHED |
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: K2 region of Karakoram | Statement: [Shaksgam Valley, nearestMajorRange, K2 region of Karakoram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorRange Context triple: [Shaksgam Valley, nearestMajorRange, K2 region of Karakoram]
-
A.
nearestMajorBase
Indicates that one location is the closest significant (major) base relative to another location.
-
B.
isNearestMajorRangeTo
chosen
Indicates that one range is the closest significant (major) range in distance or proximity to another specified location or entity.
-
C.
nearestMajorArea
Indicates the relationship where a given location is associated with the closest significant geographic or administrative area.
-
D.
nearestMajorNeighbor
Indicates that one entity is the closest significant or major neighboring entity to another in terms of spatial proximity.
-
E.
nearestMajorCenter
Indicates that one location is the closest significant urban or population center relative to another location.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 30, 2026, 11:37 p.m.