Triple
T6624203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hunter |
E149753
|
entity |
| Predicate | hasFirstAscentRoute |
P67357
|
FINISHED |
| Object | West 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: West Ridge | Statement: [Mount Hunter, hasFirstAscentRoute, West Ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstAscentRoute Context triple: [Mount Hunter, hasFirstAscentRoute, West Ridge]
-
A.
firstAscentRouteOf
chosen
Indicates that a particular climbing route is the one used for the first successful ascent of a specific peak or climbing objective.
-
B.
firstAscentStatus
Indicates whether and how a first ascent of something (such as a route, peak, or feature) has been achieved or recorded.
-
C.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
D.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
E.
hasFirstRecordedAscent
Indicates that a particular ascent is the earliest known or documented successful climb of a specific route, peak, or climbing objective.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.