Triple
T15016209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D5 Life Extension Program |
E377965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Navy 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 program Context triple: [D5 Life Extension Program, instanceOf, U.S. Navy program]
-
A.
U.S. Navy operation
A U.S. Navy operation is a coordinated maritime, air, cyber, and/or land activity conducted by the United States Navy to achieve specific military, security, or humanitarian objectives under defined rules of engagement and command structures.
-
B.
United States Air Force project
A United States Air Force project is an organized, time-bound initiative undertaken by the USAF to research, develop, test, or implement capabilities, systems, or operations in support of its strategic and tactical missions.
-
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.
United States Navy command
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.
-
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. 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:55 a.m.