Triple
T11722382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dawn Wall |
E278668
|
entity |
| Predicate | hasClimbingRoutePitches |
P2405
|
FINISHED |
| Object | 32 |
—
|
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: 32 | Statement: [The Dawn Wall, hasClimbingRoutePitches, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingRoutePitches Context triple: [The Dawn Wall, hasClimbingRoutePitches, 32]
-
A.
hasPopularAscentRouteFrom
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
-
B.
climbingRoute
chosen
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
C.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
-
D.
primaryClimbingRouteFor
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
-
E.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.