Triple
T2611751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trango Towers |
E58789
|
entity |
| Predicate | firstMajorAscentsPeriod |
P41404
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Trango Towers, firstMajorAscentsPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorAscentsPeriod Context triple: [Trango Towers, firstMajorAscentsPeriod, 1970s]
-
A.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
B.
firstAscentYear
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
C.
firstFreeAscentStartDate
Indicates the calendar date on which the first successful, previously unclimbed ascent of something (e.g., a route or peak) began.
-
D.
firstWinterAscentYear
Indicates the year in which the first successful winter ascent of something (such as a mountain or route) was completed.
-
E.
firstRecordedAscentAfter1815
Indicates that the first recorded ascent of something (typically a peak or route) occurred after the year 1815.
- F. None of above. chosen
Provenance (4 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:50 p.m.