Triple
T2693714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freerider |
E58462
|
entity |
| Predicate | ascentStyleByAlexHonnold |
P27617
|
FINISHED |
| Object | free solo |
—
|
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: free solo | Statement: [Freerider, ascentStyleByAlexHonnold, free solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascentStyleByAlexHonnold Context triple: [Freerider, ascentStyleByAlexHonnold, free solo]
-
A.
notableFreeAscentStyle
chosen
Indicates that the relationship specifies the particular style or method used for a notable free ascent of a climb or route.
-
B.
firstAscentStyle
Indicates the style or manner in which the first successful ascent of a route or peak was carried out.
-
C.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
D.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
E.
notableFreeAscentBy
Indicates that a particular free ascent (a climb done without aid for upward progress) is notably associated with or attributed to a specific climber or party.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0f43b08190a5abd936b14603b7 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.