Triple
T33269239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shore installation management command |
E851733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military shore establishment command |
C47187
|
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 shore establishment command Context triple: [shore installation management command, instanceOf, military shore establishment command]
-
A.
naval shore establishment
A naval shore establishment is a land-based facility that supports a navy’s operations, administration, training, logistics, and maintenance away from seagoing vessels.
-
B.
United States Army harbor defense command
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.
-
C.
Marine Corps base
A Marine Corps base is a military installation that provides facilities, training grounds, housing, and logistical support for United States Marine Corps personnel and operations.
-
D.
maritime support facility
A maritime support facility is a shore-based installation that provides logistical, maintenance, operational, and emergency services to vessels and maritime operations.
-
E.
military installation management organization
chosen
A military installation management organization is an entity responsible for planning, operating, maintaining, and supporting the infrastructure, services, and resources of one or more military bases to ensure mission readiness and quality of life for personnel.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.