Triple
T26608532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval District Washington |
E667847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Navy regional command |
C8187
|
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 Navy regional command Context triple: [Naval District Washington, instanceOf, United States Navy regional command]
-
A.
United States Navy command
chosen
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.
-
B.
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.
-
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.
United States Marine Corps major command
A United States Marine Corps major command is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale Marine Corps forces and operations within a defined functional or geographic area.
-
E.
United States Navy position
A United States Navy position is a specific role or billet within the Navy’s organizational structure, defined by its rank, responsibilities, and place in the chain of command.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:15 a.m.