Triple

T32307774
Position Surface form Disambiguated ID Type / Status
Subject NICA collider E825413 entity
Predicate instanceOf P0 FINISHED
Object heavy-ion collider C1693 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: heavy-ion collider
Context triple: [NICA collider, instanceOf, heavy-ion collider]
  • A. heavy-ion collision experiment
    A heavy-ion collision experiment is a high-energy physics study in which nuclei of heavy atoms are accelerated and smashed together to recreate and investigate extreme states of matter, such as quark-gluon plasma, similar to those just after the Big Bang.
  • B. heavy-ion experiment
    A heavy-ion experiment is a scientific investigation that collides nuclei of heavy atoms at high energies to study the properties of nuclear matter and the fundamental forces governing it.
  • C. hadron collider chosen
    A hadron collider is a type of particle accelerator that propels hadrons, such as protons or heavy ions, to extremely high energies and smashes them together to study fundamental particles and forces.
  • D. heavy-ion experiment subsystem
    A heavy-ion experiment subsystem is a specialized component of a larger nuclear or particle physics detector setup that performs a distinct function—such as tracking, calorimetry, triggering, or data acquisition—to measure and analyze the properties of collisions between heavy nuclei.
  • E. fixed-target particle physics experiment
    A fixed-target particle physics experiment is a setup where a beam of accelerated particles is directed onto a stationary target to study the resulting interactions and reveal fundamental properties of matter and forces.
  • 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_69f3491213b88190a57094d8697a7455 completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:45 a.m.