Triple
T26690631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dölf Reist |
E672868
|
entity |
| Predicate | dateOfFirstAscentOfLhotse |
P169241
|
FINISHED |
| Object | 1956-05-18 |
—
|
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: 1956-05-18 | Statement: [Dölf Reist, dateOfFirstAscentOfLhotse, 1956-05-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstAscentOfLhotse Context triple: [Dölf Reist, dateOfFirstAscentOfLhotse, 1956-05-18]
-
A.
summitDateOfLhotse
Indicates the date on which an ascent reached the summit of Lhotse.
-
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.
firstRecordedAscentAfter1815
Indicates that the first recorded ascent of something (typically a peak or route) occurred after the year 1815.
-
D.
firstMajorAscentOfHighestPeak
Indicates the event or relationship in which a particular ascent is recognized as the first successful major climb of the highest peak in a given context (e.g., region, range, or category).
-
E.
summitDateOfEverest
Indicates the date on which an entity reached the summit of Mount Everest.
- F. None of above. chosen
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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 27, 2026, 3:25 a.m.