Triple
T26270104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Construction Group 1 |
E657096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seabee command |
C12659
|
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: Seabee command Context triple: [Naval Construction Group 1, instanceOf, Seabee command]
-
A.
naval component command
chosen
A naval component command is a subordinate joint force command responsible for planning, directing, and coordinating naval operations within a designated theater or area of responsibility.
-
B.
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.
-
C.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
-
D.
United States Marine Corps order
A United States Marine Corps order is an official directive issued by authorized Marine Corps leadership that prescribes policies, procedures, or actions to be followed by Marines and Marine Corps units.
-
E.
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.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:12 p.m.