Triple
T36102211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltoro Kangri |
E1044241
|
entity |
| Predicate | baseTrekRoute |
P158095
|
FINISHED |
| Object | Baltoro Glacier trekking route |
—
|
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: Baltoro Glacier trekking route | Statement: [Baltoro Kangri, baseTrekRoute, Baltoro Glacier trekking route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseTrekRoute Context triple: [Baltoro Kangri, baseTrekRoute, Baltoro Glacier trekking route]
-
A.
trekkingBase
Indicates a location that serves as the primary starting point or support hub for trekking activities.
-
B.
locatedOnTrekkingRoute
chosen
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
C.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
D.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
E.
trekkingFeature
Indicates a notable characteristic, condition, or element specifically associated with trekking activities or routes.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.