Triple
T31782046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVFAC Atlantic and Pacific enterprise |
E811228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Navy shore facilities and infrastructure organization |
C18743
|
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: U.S. Navy shore facilities and infrastructure organization Context triple: [NAVFAC Atlantic and Pacific enterprise, instanceOf, U.S. Navy shore facilities and infrastructure organization]
-
A.
naval shore establishment
chosen
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 Navy systems command
The United States Navy systems command is an organizational entity responsible for developing, acquiring, and sustaining specific categories of naval systems, equipment, and technologies in support of fleet operations.
-
C.
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.
-
D.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
E.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:36 p.m.