Triple
T10180733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVFAC Northwest |
E236774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Navy shore establishment command |
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 establishment command Context triple: [NAVFAC Northwest, instanceOf, U.S. Navy shore establishment command]
-
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 command
A United States Navy command is an organizational unit, led by a designated commanding authority, responsible for directing naval personnel, resources, and operations to accomplish specific missions and functions within the Navy’s overall structure.
-
C.
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.
-
D.
U.S. Navy type command
A U.S. Navy type command is an administrative organization responsible for the readiness, training, and equipping of a specific category of naval forces, such as surface ships, submarines, or aviation units.
-
E.
United States Navy air station
A United States Navy air station is a shore-based military aviation facility operated by the U.S. Navy that supports the operation, training, maintenance, and deployment of naval aircraft and their 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:11 p.m.