Triple
T26690739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Mount Everest Expedition 1952 |
E672872
|
entity |
| Predicate | usedBottledOxygenSystem |
P33949
|
FINISHED |
| Object | closed-circuit oxygen equipment |
—
|
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: closed-circuit oxygen equipment | Statement: [Swiss Mount Everest Expedition 1952, usedBottledOxygenSystem, closed-circuit oxygen equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBottledOxygenSystem Context triple: [Swiss Mount Everest Expedition 1952, usedBottledOxygenSystem, closed-circuit oxygen equipment]
-
A.
usedSupplementaryOxygen
Indicates that an entity received or utilized additional oxygen support beyond normal atmospheric breathing, typically via medical equipment.
-
B.
usedExternalTank
chosen
Indicates that an entity made use of an external tank as part of its operation or activity.
-
C.
usedPressurizedModule
Indicates that an entity has operated or occupied a pressurized module as part of its activities or mission.
-
D.
oxygenUseCommon
Indicates that the entities typically use or rely on the same type or source of oxygen in a shared or similar manner.
-
E.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 3:25 a.m.