Triple

T21126342
Position Surface form Disambiguated ID Type / Status
Subject CEBAF Large Acceptance Spectrometer E520566 entity
Predicate hasTriggerSystem P109035 FINISHED
Object multi-level hardware trigger 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: multi-level hardware trigger | Statement: [CEBAF Large Acceptance Spectrometer, hasTriggerSystem, multi-level hardware trigger]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTriggerSystem
Context triple: [CEBAF Large Acceptance Spectrometer, hasTriggerSystem, multi-level hardware trigger]
  • A. usesTriggerSystem
    Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
  • B. hasTriggerMechanism chosen
    Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
  • C. hasTriggerType
    Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
  • D. hasVisionTrigger
    Indicates that one entity causes or initiates a vision-related response or event in another entity.
  • E. trapTrigger
    Indicates that an entity activates or sets off a trap in the environment.
  • 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_69e0b50a623881909c0bbaf4f2c055e7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72238cf708190a4676c40deea2e46 completed April 21, 2026, 7:07 a.m.
PD Predicate disambiguation batch_69e5f5ed6c8c8190b31092a5d4c3de5d completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 2:56 p.m.