Triple
T26690634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dölf Reist |
E672868
|
entity |
| Predicate | alsoClimbed |
P161955
|
FINISHED |
| Object | Mount Everest |
—
|
NE NERFINISHED |
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: Mount Everest | Statement: [Dölf Reist, alsoClimbed, Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoClimbed Context triple: [Dölf Reist, alsoClimbed, Mount Everest]
-
A.
notableClimbs
Indicates that the subject has completed or is associated with particularly significant or well-known climbing routes or ascents.
-
B.
numberOfFirstAscents
Indicates the count of times an entity has been the first to successfully ascend or climb a particular route, peak, or feature.
-
C.
usuallyClimbedAs
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
D.
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.
-
E.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
- 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_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 3:25 a.m.