Triple
T22369992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USNS Capable |
E553014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Auxiliary ship of the United States Navy |
C2335
|
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: Auxiliary ship of the United States Navy Context triple: [USNS Capable, instanceOf, Auxiliary ship of the United States Navy]
-
A.
United States Navy ship
A United States Navy ship is a commissioned naval vessel operated by the U.S. Navy, designed, equipped, and crewed to perform military, logistical, and support missions at sea and in littoral environments.
-
B.
United States Navy ship class
A United States Navy ship class is a group of naval vessels sharing a common design, construction specifications, and intended operational role within the U.S. Navy.
-
C.
naval auxiliary ship
chosen
A naval auxiliary ship is a non-combat vessel that supports naval operations by providing services such as supply, repair, transport, and logistical assistance to combat ships and shore facilities.
-
D.
United States Coast Guard cutter
A United States Coast Guard cutter is a commissioned vessel, typically 65 feet or longer, used by the Coast Guard for missions such as search and rescue, law enforcement, environmental protection, and national defense in U.S. waters and beyond.
-
E.
United States Navy submarine tender
A United States Navy submarine tender is a specialized support ship designed to provide maintenance, repair, logistical supplies, and crew services to submarines while they are at sea or in forward-deployed locations.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.