Triple
T38006439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1957 Austrian Broad Peak expedition |
E948246
|
entity |
| Predicate | elevationOfMainSummit |
P141432
|
FINISHED |
| Object | 8047 m |
—
|
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: 8047 m | Statement: [1957 Austrian Broad Peak expedition, elevationOfMainSummit, 8047 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfMainSummit Context triple: [1957 Austrian Broad Peak expedition, elevationOfMainSummit, 8047 m]
-
A.
hasMainPeakElevation_m
chosen
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an entity.
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
D.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
E.
elevationAboveSurroundingPlains
Indicates that something is situated at a higher altitude than the nearby flat or low-lying surrounding plains.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.