Triple
T37970859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanda Rutkiewicz |
E947279
|
entity |
| Predicate | firstWomanToClimb |
P1321
|
FINISHED |
| Object | K2 |
E9638
|
NE 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: K2 | Statement: [Wanda Rutkiewicz, firstWomanToClimb, K2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWomanToClimb Context triple: [Wanda Rutkiewicz, firstWomanToClimb, K2]
-
A.
firstRecordedAsClimbedBy
Indicates the person or group who is credited with making the first recorded ascent of a particular climb or peak.
-
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.
firstWinterAscentBy
Indicates that the subject was first successfully climbed in winter conditions by the specified person or party.
-
D.
madeFirstWinterAscentWith
Indicates that the subject and the object jointly completed the first successful ascent of a route or peak during winter conditions.
-
E.
firstAscentBy
chosen
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
- F. None of above.
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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42458ceba481909a160ed7379c2698 |
completed | June 29, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.