Triple

T32688317
Position Surface form Disambiguated ID Type / Status
Subject Wake Shield Facility-1 E835786 entity
Predicate vacuumLevel P174794 FINISHED
Object ultra-high vacuum in orbital wake region 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: ultra-high vacuum in orbital wake region | Statement: [Wake Shield Facility-1, vacuumLevel, ultra-high vacuum in orbital wake region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vacuumLevel
Context triple: [Wake Shield Facility-1, vacuumLevel, ultra-high vacuum in orbital wake region]
  • A. hasVacuumSystem
    Indicates that one entity is equipped with, or includes as a component, a vacuum system.
  • B. vacuumConstruction
    Indicates that an entity is involved in the construction, creation, or establishment of a vacuum or vacuum environment.
  • C. vacuumVesselMass
    Indicates the mass of the vacuum vessel associated with a given system or component.
  • D. vacuumVariantName
    Indicates that one entity is the specific variant name or labeled version of a vacuum-related item or model associated with another entity.
  • E. vakul
    Indicates a relationship or action between entities, but the specific meaning of the predicate "vakul" is unclear without additional context or definition.
  • 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_69f3493211388190993801216afbc2a7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6c81860248190ba83f2a47e2c4a67 completed May 3, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69f6c3f617c08190a70ba880210f908c completed May 3, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f6c77500a08190b2bdeca33bd2ac08 completed May 3, 2026, 3:56 a.m.
Created at: May 1, 2026, 1:09 a.m.