Triple

T21535583
Position Surface form Disambiguated ID Type / Status
Subject CERN Finance Committee E531340 entity
Predicate instanceOf P0 FINISHED
Object CERN body C15706 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: CERN body
Context triple: [CERN Finance Committee, instanceOf, CERN body]
  • A. CERN organizational unit
    A CERN organizational unit is a defined structural entity within CERN, such as a department, group, or section, responsible for specific scientific, technical, or administrative functions and reporting lines.
  • B. CERN experiment
    A CERN experiment is a large-scale, collaborative scientific investigation conducted at CERN’s particle physics facilities to study fundamental particles and forces using high-energy collisions and advanced detectors.
  • C. CERN status category
    A CERN status category represents a classification of an individual's or entity's formal relationship, role, and associated rights within the CERN organization.
  • D. CERN governance category chosen
    A CERN governance category is a classification that defines the roles, responsibilities, and decision-making authority of organizational bodies within CERN’s institutional and administrative structure.
  • E. CERN accelerator complex component
    A CERN accelerator complex component is a specialized physical or control-system element—such as magnets, RF cavities, beamlines, detectors, or power and cooling infrastructure—that collectively enables the production, acceleration, steering, and monitoring of particle beams for experimental research.
  • F. None of above.

Provenance (1 batch)

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_69e0c45e5b8881908ac18fc2f493b114 completed April 16, 2026, 11:13 a.m.
Created at: April 16, 2026, 6:27 p.m.