Triple
T26474705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAMA 300 gravitational wave detector |
E665995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gravitational wave detector |
C51623
|
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: gravitational wave detector Context triple: [TAMA 300 gravitational wave detector, instanceOf, gravitational wave detector]
-
A.
second-generation gravitational-wave detector
A second-generation gravitational-wave detector is an advanced interferometric observatory, such as Advanced LIGO or Advanced Virgo, designed with enhanced sensitivity and noise reduction to detect weaker and more distant gravitational-wave signals than first-generation instruments.
-
B.
gravitational-wave collaboration
A gravitational-wave collaboration is a large, coordinated international team of scientists, engineers, and institutions that design, operate, and analyze data from detectors to discover and study gravitational waves.
-
C.
neutrino detector
A neutrino detector is a highly sensitive instrument or facility designed to observe and measure elusive neutrinos by capturing their rare interactions with matter, often deep underground or underwater to shield from background radiation.
-
D.
particle detector
A particle detector is a device or system that identifies, tracks, and measures properties of subatomic particles produced in physical processes or experiments.
-
E.
torsion seismometer
A torsion seismometer is an instrument that detects and measures ground motion by sensing the rotational (torsional) response of a suspended mass to seismic waves.
- F. None of above. chosen
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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:22 a.m.