Triple
T30312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Station HYPO |
E605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cryptanalysis unit |
C699
|
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: cryptanalysis unit Context triple: [Station HYPO, instanceOf, cryptanalysis unit]
-
A.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
B.
research prototype
A research prototype is an early, often experimental implementation of a concept or system created to explore feasibility, validate ideas, and gather feedback before full-scale development.
-
C.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
-
D.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
E.
heterodyne receiver
A heterodyne receiver is a radio receiver that converts an incoming signal to an intermediate frequency by mixing it with a locally generated oscillator signal to enable easier and more selective amplification and filtering.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.