Triple
T33552353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Mount Everest disaster |
E859371
|
entity |
| Predicate | highestCampAffected |
P140841
|
FINISHED |
| Object | South Col |
—
|
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: South Col | Statement: [1996 Mount Everest disaster, highestCampAffected, South Col]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestCampAffected Context triple: [1996 Mount Everest disaster, highestCampAffected, South Col]
-
A.
higherCamp
Indicates that one camp is located at a higher elevation or position relative to another camp.
-
B.
hasHighCampOn
Indicates that one entity maintains or has established a primary or elevated campsite located on another entity (typically a mountain or route).
-
C.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
D.
highestCampAltitudeMetres
chosen
Indicates the maximum altitude in meters reached by any camp associated with the entity.
-
E.
highestPeakAccessible
Indicates that one location is the tallest peak that can be reached or accessed from another specified location or by a specified agent.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:39 a.m.