Triple
T11331384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimborazo summit expeditions |
E268350
|
entity |
| Predicate | commonAscentStyle |
P45129
|
FINISHED |
| Object | guided climb |
—
|
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: guided climb | Statement: [Chimborazo summit expeditions, commonAscentStyle, guided climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAscentStyle Context triple: [Chimborazo summit expeditions, commonAscentStyle, guided climb]
-
A.
typicalAscentStyle
chosen
Indicates the usual or characteristic manner or technique by which an ascent or climb is performed.
-
B.
notableFreeAscentStyle
Indicates that the relationship specifies the particular style or method used for a notable free ascent of a climb or route.
-
C.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
D.
towerStyle
Indicates the architectural or design style that characterizes a given tower.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.