Triple
T17555818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Mission Program |
E427587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Military Sealift Command program |
C34653
|
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: Military Sealift Command program Context triple: [Special Mission Program, instanceOf, Military Sealift Command program]
-
A.
U.S. Navy program
chosen
A U.S. Navy program is an organized, formally managed initiative that develops, acquires, sustains, or improves naval capabilities, systems, or operations to support the Navy’s strategic and operational objectives.
-
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.
naval shipbuilding program
A naval shipbuilding program is an organized, long-term initiative to design, construct, and deliver warships and support vessels to meet a navy’s strategic, operational, and technological requirements.
-
D.
United States Navy construction force
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.
-
E.
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.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.