Triple
T38006410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 Nanga Parbat expedition |
E948245
|
entity |
| Predicate | hasMainPeakHeight |
P141432
|
FINISHED |
| Object | 8126 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: 8126 m | Statement: [1953 Nanga Parbat expedition, hasMainPeakHeight, 8126 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPeakHeight Context triple: [1953 Nanga Parbat expedition, hasMainPeakHeight, 8126 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.
hasMainMountain
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
C.
hasHighestPeakHeight
Indicates that the subject entity possesses the greatest peak height compared to all other relevant entities in the given context.
-
D.
hasHighestPeaksOver
Indicates that one entity possesses mountain peaks that are higher in elevation than those of another entity.
-
E.
hasHighestPoint_m
Indicates that an entity possesses a highest point whose elevation is measured in meters.
- 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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.