Triple
T2590025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose |
E58098
|
entity |
| Predicate | ascendsFeature |
P6286
|
FINISHED |
| Object | central prow of El Capitan |
—
|
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: central prow of El Capitan | Statement: [The Nose, ascendsFeature, central prow of El Capitan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendsFeature Context triple: [The Nose, ascendsFeature, central prow of El Capitan]
-
A.
elevatedFeature
Indicates that one feature or element is positioned or raised higher relative to another reference level or surrounding context.
-
B.
crestFeature
Indicates that an entity possesses a notable crest-related characteristic or structural feature.
-
C.
notableAscent
chosen
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
D.
ascensionMethod
Indicates the means or process by which an entity rises, advances, or transitions to a higher state, level, or position.
-
E.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3feb45c81909369a49c3990294a |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.