Triple
T16771903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCGC Taney |
E407617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Coast Guard cutter |
C12207
|
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: Coast Guard cutter Context triple: [USCGC Taney, instanceOf, Coast Guard cutter]
-
A.
United States Coast Guard cutter
chosen
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.
-
B.
Gleaves-class destroyer
The Gleaves-class destroyer was a World War II-era United States Navy class of fast, versatile destroyers designed for anti-submarine warfare, convoy escort, and fleet screening operations.
-
C.
Edsall-class destroyer escort
The Edsall-class destroyer escort was a World War II-era class of U.S. Navy escort ships designed primarily for anti-submarine warfare and convoy protection in the Atlantic and Pacific theaters.
-
D.
Bagley-class destroyer
A Bagley-class destroyer is a type of U.S. Navy warship built in the late 1930s, characterized by high speed, heavy torpedo armament, and service in World War II as an escort and attack vessel.
-
E.
Pensacola-class cruiser
The Pensacola-class cruiser was a pair of early U.S. Navy "treaty cruisers" built in the late 1920s, characterized by heavy 8-inch guns, relatively light armor, and high speed, serving prominently in the Pacific during World War II.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.