Triple
T7817912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor defenses of New York |
E181057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military installation network |
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 installation network Context triple: [Harbor defenses of New York, instanceOf, military installation network]
-
A.
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.
-
B.
U.S. Department of Defense network
A U.S. Department of Defense network is a secure, government-operated information and communications infrastructure used to support military operations, intelligence, logistics, and administrative functions across classified and unclassified environments.
-
C.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
-
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.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:40 p.m.