Triple
T2462734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Whymper |
E54568
|
entity |
| Predicate | dateOfFirstAscent |
P8812
|
FINISHED |
| Object | 1865-07-14 |
—
|
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: 1865-07-14 | Statement: [Edward Whymper, dateOfFirstAscent, 1865-07-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstAscent Context triple: [Edward Whymper, dateOfFirstAscent, 1865-07-14]
-
A.
firstAscentYear
chosen
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
B.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
C.
usualFirstAscentBy
Indicates that the referenced entity is the person or party who is typically credited with making the first ascent of a particular route, peak, or climbing objective.
-
D.
firstWinterAscentBy
Indicates that the subject was first successfully climbed in winter conditions by the specified person or party.
-
E.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.