Triple
T15928690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunanyi |
E386268
|
entity |
| Predicate | hasFirstRecordedEuropeanAscentYear |
P39708
|
FINISHED |
| Object | 1798 |
—
|
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: 1798 | Statement: [Kunanyi, hasFirstRecordedEuropeanAscentYear, 1798]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstRecordedEuropeanAscentYear Context triple: [Kunanyi, hasFirstRecordedEuropeanAscentYear, 1798]
-
A.
firstRecordedAsClimbedBy
Indicates the person or group who is credited with making the first recorded ascent of a particular climb or peak.
-
B.
hasFirstRecordedAscent
Indicates that a particular ascent is the earliest known or documented successful climb of a specific route, peak, or climbing objective.
-
C.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
D.
firstAscentByEuropeans
chosen
Indicates that the referenced event or location was first successfully ascended or reached by European individuals or expeditions.
-
E.
firstFreeAscentOfTheNoseBy
Indicates that the subject is the climber or party who made the first free ascent of the route known as “The Nose.”
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.