Triple
T13300562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma-ray Burst Monitor |
E316799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysics experiment |
C11704
|
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: astrophysics experiment Context triple: [Gamma-ray Burst Monitor, instanceOf, astrophysics experiment]
-
A.
cosmology experiment
A cosmology experiment is a scientific investigation designed to measure and analyze cosmic phenomena—such as the cosmic microwave background, large-scale structure, or dark energy—to test and refine models of the universe’s origin, composition, and evolution.
-
B.
space experiment
chosen
A space experiment is a controlled scientific investigation conducted in the unique conditions of outer space or microgravity to study physical, biological, or technological phenomena not observable or easily replicated on Earth.
-
C.
radio astronomy experiment
A radio astronomy experiment is a scientific investigation that uses radio telescopes and related instrumentation to detect, measure, and analyze radio waves from celestial sources to study the universe.
-
D.
physics experiment
A physics experiment is a controlled procedure designed to test hypotheses, observe phenomena, and measure physical quantities to understand the laws governing the natural world.
-
E.
nuclear physics experiment
A nuclear physics experiment is a controlled scientific investigation that probes the properties, interactions, and structure of atomic nuclei using particle beams, detectors, and specialized instrumentation.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:28 p.m.