Triple
T34982924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Estcourt |
E1008862
|
entity |
| Predicate | diedDuringExpedition |
P101384
|
FINISHED |
| Object | 1978 British K2 expedition |
—
|
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: 1978 British K2 expedition | Statement: [Nick Estcourt, diedDuringExpedition, 1978 British K2 expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diedDuringExpedition Context triple: [Nick Estcourt, diedDuringExpedition, 1978 British K2 expedition]
-
A.
diedDuringExpeditionOn
chosen
Indicates that an entity died while participating in a specific expedition that took place on a given date.
-
B.
diedDuringExpeditionTo
Indicates that an entity died while participating in or as a consequence of a specific expedition to a particular place or destination.
-
C.
diedOnJourneyBetween
Indicates that an entity died while traveling between two specified locations or points in a journey.
-
D.
diedInExile
Indicates that an entity died while living away from their native or home country, typically as a result of banishment, forced displacement, or self-imposed exile.
-
E.
diedOnShip
Indicates that an entity died while on board a ship.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.