Triple
T12435330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Hall Station, Virginia |
E297129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military intelligence facility |
C14870
|
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: military intelligence facility Context triple: [Arlington Hall Station, Virginia, instanceOf, military intelligence facility]
-
A.
signals intelligence facility
A signals intelligence facility is a secure installation equipped with specialized systems and personnel dedicated to intercepting, processing, analyzing, and disseminating electronic communications and emissions for intelligence and security purposes.
-
B.
intelligence agency facility
chosen
An intelligence agency facility is a secure, specialized complex where classified information is collected, analyzed, stored, and operations are coordinated to support national security and intelligence objectives.
-
C.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
D.
weapons testing facility
A weapons testing facility is a secure, controlled site where weapons and related systems are developed, evaluated, and tested for performance, safety, and reliability.
-
E.
defense intelligence organization
A defense intelligence organization is a specialized governmental or military entity responsible for collecting, analyzing, and disseminating information on foreign and domestic threats to support national security and defense decision-making.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.