Triple
T26270105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Construction Group 1 |
E657096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval construction force command |
C34029
|
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: naval construction force command Context triple: [Naval Construction Group 1, instanceOf, naval construction force command]
-
A.
United States Navy construction force
chosen
The United States Navy construction force, commonly known as the Seabees, is a military engineering organization responsible for building and maintaining naval bases, airfields, and other critical infrastructure in support of naval and joint operations worldwide.
-
B.
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.
-
C.
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.
-
D.
naval shore establishment
A naval shore establishment is a land-based facility that supports a navy’s operations, administration, training, logistics, and maintenance away from seagoing vessels.
-
E.
naval design organization
A naval design organization is an entity responsible for conceiving, developing, and integrating the technical, structural, and systems designs of naval vessels to meet specified operational, safety, and regulatory requirements.
- 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.