Triple
T8665103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Meyer |
E205648
|
entity |
| Predicate | yearOfFirstAscent |
P8812
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Hans Meyer, yearOfFirstAscent, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFirstAscent Context triple: [Hans Meyer, yearOfFirstAscent, 1889]
-
A.
firstAscentYear
chosen
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
B.
firstWinterAscentYear
Indicates the year in which the first successful winter ascent of something (such as a mountain or route) was completed.
-
C.
firstWinterAscentBy
Indicates that the subject was first successfully climbed in winter conditions by the specified person or party.
-
D.
firstRecordedAsClimbedBy
Indicates the person or group who is credited with making the first recorded ascent of a particular climb or peak.
-
E.
coFirstAscentOf
Indicates that multiple climbers or parties share credit for making the first recorded ascent of a particular route, peak, or climbing objective.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a0ae108190b33dadcc3cb18949 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.