Triple
T7282533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ready Reserve Force |
E163785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sealift reserve fleet |
C20621
|
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: sealift reserve fleet Context triple: [Ready Reserve Force, instanceOf, sealift reserve fleet]
-
A.
sealift reserve
A sealift reserve is a strategic pool of ships, crews, and related resources maintained to provide additional maritime transport capacity for military or emergency logistics when regular commercial or military sealift is insufficient.
-
B.
sealift fleet
A sealift fleet is a collection of cargo and support vessels organized to transport military or commercial goods and equipment across seas and oceans.
-
C.
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.
-
D.
component of the National Defense Reserve Fleet
chosen
A component of the National Defense Reserve Fleet is a designated group of government-owned, militarily useful merchant vessels maintained in a specific location for rapid activation in support of national defense and emergency sealift needs.
-
E.
National Defense Reserve Fleet anchorage
A National Defense Reserve Fleet anchorage is a designated harbor area where the U.S. government moors and maintains inactive merchant and military support vessels for rapid activation during national emergencies or defense needs.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:59 p.m.