Triple
T9441055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVFAC Marianas |
E227645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Naval Facilities Engineering Systems Command component |
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: Naval Facilities Engineering Systems Command component Context triple: [NAVFAC Marianas, instanceOf, Naval Facilities Engineering Systems Command component]
-
A.
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.
-
B.
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.
-
C.
naval component command
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.
-
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 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.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:50 p.m.