Triple
T18700030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Couloir |
E457221
|
entity |
| Predicate | isClimbedAs |
P74334
|
FINISHED |
| Object | alpine 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: alpine route | Statement: [North Couloir, isClimbedAs, alpine route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbedAs Context triple: [North Couloir, isClimbedAs, alpine route]
-
A.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
B.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
C.
isClimbedIn
Indicates that an entity (typically a person or animal) ascends or climbs while being located within or inside another entity (such as a structure, vehicle, or environment).
-
D.
usuallyClimbedAs
chosen
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
E.
climbedWith
Indicates that one entity climbed together with another entity, sharing the ascent as a joint activity.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562eb06b481908ef9efdb976008f3 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.