Triple
T21438185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBARS |
E528868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Navy acquisition 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: U.S. Navy acquisition program Context triple: [CBARS, instanceOf, U.S. Navy acquisition 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.
U.S. Military Sealift Command program
The U.S. Military Sealift Command program is a logistical and support organization that operates and manages civilian-crewed ships to provide ocean transportation, replenishment, and specialized maritime services for U.S. military forces worldwide.
-
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 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.
-
E.
Royal Navy programme
A Royal Navy programme is an organized initiative or plan undertaken by the Royal Navy to develop, maintain, or enhance its capabilities, operations, personnel, or infrastructure over a defined period.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:04 p.m.