Triple
T7570113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Mount Everest/Lhotse Expedition 1956 |
E179216
|
entity |
| Predicate | summitTeamForEverest |
P33975
|
FINISHED |
| Object | Ernst Schmied |
—
|
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: Ernst Schmied | Statement: [Swiss Mount Everest/Lhotse Expedition 1956, summitTeamForEverest, Ernst Schmied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitTeamForEverest Context triple: [Swiss Mount Everest/Lhotse Expedition 1956, summitTeamForEverest, Ernst Schmied]
-
A.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
B.
reachesSummitOf
Indicates that one entity successfully arrives at or attains the highest point or summit of another entity.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
reachedSummitWith
chosen
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
E.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f920540c8190817712db5aa3eeff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.