Triple
T15115905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mytikas |
E361037
|
entity |
| Predicate | seasonBestForAscent |
P1325
|
FINISHED |
| Object | summer |
—
|
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 | Statement: [Mytikas, seasonBestForAscent, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonBestForAscent Context triple: [Mytikas, seasonBestForAscent, summer]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
winterAscent
Indicates an ascent or climb that is carried out during the winter season, under winter conditions.
-
C.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
D.
winterAscentFirstBy
Indicates that the referenced ascent is the first successful climb of a route, peak, or face carried out specifically in winter conditions by the specified climber or party.
-
E.
secondAscentBy
Indicates that the related entity is the person, group, or expedition that made the second successful 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.