Triple
T12665500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South-Southeast Ridge of K2 |
E302541
|
entity |
| Predicate | climbedInSeason |
P1325
|
FINISHED |
| Object | summer climbing season on K2 |
—
|
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: summer climbing season on K2 | Statement: [South-Southeast Ridge of K2, climbedInSeason, summer climbing season on K2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbedInSeason Context triple: [South-Southeast Ridge of K2, climbedInSeason, summer climbing season on K2]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
climbedWith
Indicates that one entity climbed together with another entity, sharing the ascent as a joint activity.
-
C.
climbedIn
Indicates that one entity moved upward to enter or get inside another entity, typically by climbing.
-
D.
isClimbedAllYear
Indicates that the subject is climbed continuously or is suitable for climbing throughout the entire year, without a specific season.
-
E.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617e030881908444743b8a7e0d75 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.