Triple
T29104455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor Defenses of Puget Sound |
E736724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army coast artillery command |
C51898
|
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: United States Army coast artillery command Context triple: [Harbor Defenses of Puget Sound, instanceOf, United States Army coast artillery command]
-
A.
United States Army harbor defense command
chosen
A United States Army harbor defense command was a specialized organizational unit responsible for planning, coordinating, and executing the coastal and harbor defense of a specific port or maritime area, including fixed fortifications, minefields, and supporting artillery.
-
B.
artillery corps
An artillery corps is a military formation specialized in operating heavy weapons such as cannons, howitzers, and rocket systems to deliver long-range indirect fire support on the battlefield.
-
C.
U.S. Army sustainment command
The U.S. Army Sustainment Command is the organization responsible for providing logistics, supply, maintenance, and distribution support to ensure Army forces are equipped and sustained during training, deployment, and combat operations worldwide.
-
D.
artillery unit
An artillery unit is a military formation equipped with long-range weapons designed to deliver indirect fire support against enemy targets from protected or distant positions.
-
E.
corps artillery headquarters
A corps artillery headquarters is the command element responsible for planning, coordinating, and controlling all artillery and fire support operations within a military corps.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:14 a.m.