Triple
T18817669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HARP |
E460179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radio astronomy receiver |
C406
|
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: radio astronomy receiver Context triple: [HARP, instanceOf, radio astronomy receiver]
-
A.
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.
-
B.
radio interferometer observatory
A radio interferometer observatory is a facility that combines signals from multiple spatially separated radio antennas to synthesize a much larger effective telescope for high-resolution observations of celestial radio sources.
-
C.
radio astronomy technique
A radio astronomy technique is a method or procedure used to detect, measure, and analyze radio waves from celestial sources to study the physical properties and behavior of astronomical objects and phenomena.
-
D.
radio telescope configuration
A radio telescope configuration is the specific arrangement and technical setup of one or more radio antennas, receivers, and associated systems designed to optimize the detection and imaging of radio signals from astronomical sources.
-
E.
radio receiver architecture
chosen
A radio receiver architecture is the conceptual design and organization of functional blocks and signal paths that determine how a receiver selects, downconverts, filters, and demodulates radio-frequency signals into usable information.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:55 a.m.