Triple
T32780011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Tower |
E838325
|
entity |
| Predicate | hasClimbingElement |
P192584
|
FINISHED |
| Object | attempt to scale an unclimbed peak |
—
|
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: attempt to scale an unclimbed peak | Statement: [The White Tower, hasClimbingElement, attempt to scale an unclimbed peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingElement Context triple: [The White Tower, hasClimbingElement, attempt to scale an unclimbed peak]
-
A.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
B.
hasClimbType
Indicates the specific style or category of climbing associated with a given climbing route or activity.
-
C.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
D.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
-
E.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
- F. None of above. chosen
Provenance (4 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 1, 2026, 1:14 a.m.