Triple
T17555865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Sealift Officer Program |
E427588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Navy Reserve 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 Reserve program Context triple: [Strategic Sealift Officer Program, instanceOf, U.S. Navy Reserve 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.
naval reserve force
A naval reserve force is a component of a nation's navy composed of trained personnel who serve part-time and can be mobilized to support or augment regular naval operations during emergencies, conflicts, or special missions.
-
C.
U.S. Navy staff code
A U.S. Navy staff code is a standardized alphanumeric designation that identifies the specific functional area, responsibility, or staff section within a naval command’s organizational structure.
-
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 community
A U.S. Navy community is a group of sailors and officers organized around a specific warfare area, specialty, or professional focus, sharing common training, qualifications, and career paths within the Navy.
- 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.