Triple
T36415565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Oglethorpe (AKA-100) |
E896992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Andromeda-class attack cargo ship |
C63546
|
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: Andromeda-class attack cargo ship Context triple: [USS Oglethorpe (AKA-100), instanceOf, Andromeda-class attack cargo ship]
-
A.
Federation transport ship
A Federation transport ship is a starship designed primarily for the safe and efficient movement of personnel, cargo, and supplies between worlds and installations within the Federation.
-
B.
Danae-class light cruiser
The Danae-class light cruiser was a group of British Royal Navy warships built during and shortly after World War I, designed for fleet scouting and trade protection with improved armament and speed over preceding light cruiser classes.
-
C.
Leander-class light cruiser
The Leander-class light cruiser was a group of British Royal Navy warships built in the 1930s, designed as fast, versatile cruisers for trade protection, fleet screening, and colonial patrol duties.
-
D.
Kuma-class light cruiser
The Kuma-class light cruiser was a group of early 20th-century Japanese warships designed for high-speed scouting and torpedo attacks, serving in various roles throughout the interwar period and World War II.
-
E.
Leander-class cruiser
The Leander-class cruiser was a group of British light cruisers built in the 1930s, designed for trade protection and fleet duties, and widely employed by the Royal Navy and Commonwealth navies during World War II.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.