Triple
T22388773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Ridge route on Mount Everest |
E553461
|
entity |
| Predicate | commonlyUsesSupplementalOxygen |
P77837
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Southeast Ridge route on Mount Everest, commonlyUsesSupplementalOxygen, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsesSupplementalOxygen Context triple: [Southeast Ridge route on Mount Everest, commonlyUsesSupplementalOxygen, true]
-
A.
usedSupplementaryOxygen
chosen
Indicates that an entity received or utilized additional oxygen support beyond normal atmospheric breathing, typically via medical equipment.
-
B.
oxygenationIndicator
Indicates that something serves as a marker or measure of the presence, level, or status of oxygenation in a system or process.
-
C.
oxygenUseCommon
Indicates that the entities typically use or rely on the same type or source of oxygen in a shared or similar manner.
-
D.
oxygenationLevelOfBlood
Indicates the degree to which oxygen is present in the blood.
-
E.
oxygenationChange
Indicates a change in the level or state of oxygenation associated with an entity or process.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15858c13c819098fe66a50ecea7d7 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.