Triple
T11114107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Communications Annex |
E262838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military communications facility |
C1086
|
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 communications facility Context triple: [Naval Communications Annex, instanceOf, military communications facility]
-
A.
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.
-
B.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
C.
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.
-
D.
deep space communications facility
A deep space communications facility is a ground-based complex equipped with large antennas, high-power transmitters, and sensitive receivers used to send commands to and receive data from spacecraft operating far beyond Earth's orbit.
-
E.
former military complex
A former military complex is a decommissioned installation once used for defense or armed forces operations, now repurposed, abandoned, or awaiting redevelopment.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.