Triple
T37936278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Nanga Parbat rescue of Élisabeth Revol |
E946358
|
entity |
| Predicate | rescuer |
P7320
|
FINISHED |
| Object | Denis Urubko |
—
|
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: Denis Urubko | Statement: [2018 Nanga Parbat rescue of Élisabeth Revol, rescuer, Denis Urubko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuer Context triple: [2018 Nanga Parbat rescue of Élisabeth Revol, rescuer, Denis Urubko]
-
A.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
B.
usedMeansToRescue
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
-
C.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
D.
rescuedBy
chosen
Indicates that one entity has been saved or brought out of danger by another entity.
-
E.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.