Triple
T27645503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunkun |
E696701
|
entity |
| Predicate | firstAscentOfKun |
P1320
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [Nunkun, firstAscentOfKun, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentOfKun Context triple: [Nunkun, firstAscentOfKun, 1913]
-
A.
firstAscentRouteOf
Indicates that a particular climbing route is the one used for the first successful ascent of a specific peak or climbing objective.
-
B.
attemptedFirstAscentOf
Indicates that an entity made an effort to be the first to successfully climb or reach the summit of a particular route, peak, or feature.
-
C.
firstAscent
chosen
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
D.
firstAscentFrom
Indicates the starting location or route from which the first successful ascent of something (typically a peak or climb) was made.
-
E.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: April 27, 2026, 2:29 p.m.