Triple
T2611764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trango Towers |
E58789
|
entity |
| Predicate | trekApproach |
P6174
|
FINISHED |
| Object | via Baltoro Glacier |
—
|
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: via Baltoro Glacier | Statement: [Trango Towers, trekApproach, via Baltoro Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekApproach Context triple: [Trango Towers, trekApproach, via Baltoro Glacier]
-
A.
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.
-
B.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
C.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
D.
approachRoute
chosen
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
E.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.