Triple
T11784755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K3 |
E280241
|
entity |
| Predicate | standardBaseCampAccess |
P73667
|
FINISHED |
| Object | Trek 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: Trek via Baltoro Glacier | Statement: [K3, standardBaseCampAccess, Trek via Baltoro Glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardBaseCampAccess Context triple: [K3, standardBaseCampAccess, Trek via Baltoro Glacier]
-
A.
typicalBaseCampArea
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
-
B.
hasBackcountryAccess
chosen
Indicates that an entity provides or permits access to undeveloped, remote, or wilderness areas typically used for backcountry activities.
-
C.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
D.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
E.
hasBackcountryGate
Indicates that an entity provides or is equipped with an access gate leading into a backcountry or undeveloped area.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a585795c8190aa8a5edf0d99b47f |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.