Triple
T26990387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type Commands |
E679848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Navy organizational structure |
C8979
|
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 organizational structure Context triple: [Type Commands, instanceOf, United States Navy organizational structure]
-
A.
naval command structure
A naval command structure is the hierarchical organization of authority, responsibility, and communication within a navy that directs the planning, coordination, and execution of maritime operations.
-
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.
U.S. Navy formation
A U.S. Navy formation is an organized arrangement of naval vessels or aircraft maneuvering together under a unified command to achieve tactical, operational, or ceremonial objectives at sea or in the air.
-
D.
U.S. Navy type command
chosen
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 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.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:51 a.m.