Triple
T21184602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Peak |
E522046
|
entity |
| Predicate | ridgeFeature |
P105763
|
FINISHED |
| Object | Knife Edge connects K2 to main summit ridge |
—
|
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: Knife Edge connects K2 to main summit ridge | Statement: [Capitol Peak, ridgeFeature, Knife Edge connects K2 to main summit ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ridgeFeature Context triple: [Capitol Peak, ridgeFeature, Knife Edge connects K2 to main summit ridge]
-
A.
ridgeComponent
chosen
Indicates that one entity is a structural or functional part of a ridge associated with another entity.
-
B.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
C.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
D.
crestFeature
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
-
E.
isRidge
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e730205ce88190b0bb33003295d6e7 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:06 p.m.