Triple
T17555734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Support Program |
E427585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Military Sealift Command program |
C39104
|
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: U.S. Military Sealift Command program Context triple: [Service Support Program, instanceOf, U.S. Military Sealift Command program]
-
A.
U.S. Navy program
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 freight program
A United States freight program is a coordinated set of policies, investments, and initiatives designed to improve the efficiency, safety, capacity, and environmental performance of the nation’s freight transportation system across modes such as trucking, rail, maritime, and air cargo.
-
C.
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.
-
D.
maritime patrol aircraft program
A maritime patrol aircraft program is an organized effort to design, acquire, operate, and sustain aircraft and supporting systems dedicated to long-range surveillance, anti-submarine warfare, and protection of maritime domains.
-
E.
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.
- F. None of above. chosen
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.