Triple
T28184921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond face routes |
E716149
|
entity |
| Predicate | firstFreeClimbsEra |
P145485
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Diamond face routes, firstFreeClimbsEra, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFreeClimbsEra Context triple: [Diamond face routes, firstFreeClimbsEra, 1960s]
-
A.
climbingEra
chosen
Indicates the historical period or era during which a climbing activity, style, or achievement took place.
-
B.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
C.
firstFreeAscentStartDate
Indicates the calendar date on which the first successful, previously unclimbed ascent of something (e.g., a route or peak) began.
-
D.
numberOfFirstAscents
Indicates the count of times an entity has been the first to successfully ascend or climb a particular route, peak, or feature.
-
E.
firstFreeAscentDate
Indicates the date on which the first successful ascent of a route, peak, or climb was completed without the use of artificial aids for upward progress.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: April 27, 2026, 10:22 p.m.