Triple
T26335797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First recorded ascent of Ball's Pyramid |
E662513
|
entity |
| Predicate | leadClimber |
P159935
|
FINISHED |
| Object | David Witham |
—
|
NE NERFINISHED |
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: David Witham | Statement: [First recorded ascent of Ball's Pyramid, leadClimber, David Witham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadClimber Context triple: [First recorded ascent of Ball's Pyramid, leadClimber, David Witham]
-
A.
leadClimber
chosen
Indicates that one climber is acting as the primary or front climber responsible for leading a climbing route relative to another entity or context.
-
B.
typeOfClimber
Indicates the specific category or style of climbing that a climber practices or is associated with.
-
C.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
-
D.
includedClimber
Indicates that a climber is part of, or counted within, a specified group, set, or collection of climbers.
-
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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f6cf3208190816114685e00e96c |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:36 p.m.