Triple
T34389137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Günther Messner |
E882641
|
entity |
| Predicate | mountainInvolvedInDeath |
P179153
|
FINISHED |
| Object | Nanga Parbat |
—
|
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: Nanga Parbat | Statement: [Günther Messner, mountainInvolvedInDeath, Nanga Parbat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainInvolvedInDeath Context triple: [Günther Messner, mountainInvolvedInDeath, Nanga Parbat]
-
A.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
-
B.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
C.
mountainHeight
Indicates the vertical elevation or height of a mountain, typically measured from sea level.
-
D.
mountainAccess
Indicates that an entity has the ability, right, or means to reach, enter, or utilize a mountain or mountainous area.
-
E.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:59 a.m.