Triple
T33552369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Mount Everest disaster |
E859371
|
entity |
| Predicate | notableAccount |
—
|
GENERATED |
| Object | Into Thin Air |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAccount Context triple: [1996 Mount Everest disaster, notableAccount, Into Thin Air]
-
A.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
B.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
C.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
notableFriend
Indicates that one entity is a friend of another in a way that is especially prominent, well-known, or significant.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:39 a.m.