Triple
T25953948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1970 Nanga Parbat expedition |
E654044
|
entity |
| Predicate | causeOfDeathOfGüntherMessner |
P144
|
FINISHED |
| Object | avalanche |
—
|
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: avalanche | Statement: [1970 Nanga Parbat expedition, causeOfDeathOfGüntherMessner, avalanche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathOfGüntherMessner Context triple: [1970 Nanga Parbat expedition, causeOfDeathOfGüntherMessner, avalanche]
-
A.
diedDuringExpeditionOn
Indicates that an entity died while participating in a specific expedition that took place on a given date.
-
B.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
C.
diedDuringExpeditionTo
Indicates that an entity died while participating in or as a consequence of a specific expedition to a particular place or destination.
-
D.
causeOfHusbandDeath
Indicates that the subject is the cause or reason for the husband’s death.
-
E.
deifiedPersonDeathCause
Indicates the cause or manner of death of the person who is venerated or treated as a deity.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 8:44 a.m.