Triple

T7491089
Position Surface form Disambiguated ID Type / Status
Subject 1955 British Kangchenjunga expedition E177005 entity
Predicate usedSupplementaryOxygen P77837 FINISHED
Object yes 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: yes | Statement: [1955 British Kangchenjunga expedition, usedSupplementaryOxygen, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedSupplementaryOxygen
Context triple: [1955 British Kangchenjunga expedition, usedSupplementaryOxygen, yes]
  • A. oxygenUseCommon
    Indicates that the entities typically use or rely on the same type or source of oxygen in a shared or similar manner.
  • B. oxygenValueApprox
    Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
  • C. oxygenRequirement
    Indicates the level or type of oxygen needed by an entity to live, function, or operate.
  • D. mayHaveAccessoryRespiration
    Indicates that an entity can exhibit or be associated with an additional or auxiliary form of respiration beyond its primary respiratory process.
  • E. hasSupplement
    Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
  • F. None of above. chosen

Provenance (4 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_69c69f2583808190bd1a4936c42a5815 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f81b431481908214b69c6c8d83bc completed March 27, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69c6f4d266d88190982cf5d2ee2e9564 completed March 27, 2026, 9:21 p.m.
PDg Predicate description generation batch_69c6f8184bb08190b2f70545a6aa277c completed March 27, 2026, 9:35 p.m.
Created at: March 27, 2026, 3:43 p.m.