Triple
T11971798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hushe Valley |
E284936
|
entity |
| Predicate | trekConnection |
P14127
|
FINISHED |
| Object | route to Concordia via Gondogoro La |
—
|
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: route to Concordia via Gondogoro La | Statement: [Hushe Valley, trekConnection, route to Concordia via Gondogoro La]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekConnection Context triple: [Hushe Valley, trekConnection, route to Concordia via Gondogoro La]
-
A.
trekType
Indicates the specific category or style of trekking activity associated with an entity.
-
B.
trekStage
Indicates a specific segment or leg within a longer trek or journey, typically ordered as part of a multi-stage route.
-
C.
trekSeason
Indicates that something occurs during, is associated with, or is designated as a particular season of a trek or trekking activity.
-
D.
TrailLinkIs
chosen
Indicates that one trail segment is connected to or continues from another trail segment.
-
E.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.