Triple
T8711620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 British Mount Everest expedition |
E206789
|
entity |
| Predicate | usedOxygen |
P77837
|
FINISHED |
| Object | supplementary oxygen |
—
|
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: supplementary oxygen | Statement: [1953 British Mount Everest expedition, usedOxygen, supplementary oxygen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOxygen Context triple: [1953 British Mount Everest expedition, usedOxygen, supplementary oxygen]
-
A.
usedSupplementaryOxygen
chosen
Indicates that an entity received or utilized additional oxygen support beyond normal atmospheric breathing, typically via medical equipment.
-
B.
oxygenUseCommon
Indicates that the entities typically use or rely on the same type or source of oxygen in a shared or similar manner.
-
C.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
D.
oxygenRequirement
Indicates the level or type of oxygen needed by an entity to live, function, or operate.
-
E.
usedExternalTank
Indicates that an entity made use of an external tank as part of its operation or activity.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.