Triple
T23727809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YOGN-42 concrete barge |
E586327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II–era vessel |
C47991
|
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: World War II–era vessel Context triple: [YOGN-42 concrete barge, instanceOf, World War II–era vessel]
-
A.
World War II-era ship
A World War II-era ship is a naval or auxiliary vessel designed, built, or actively used between 1939 and 1945 for military, logistical, or support roles in the global conflict of the Second World War.
-
B.
World War II merchant ship
A World War II merchant ship is a civilian cargo or transport vessel used during the Second World War to move troops, supplies, and materials across seas, often under threat from enemy submarines and aircraft.
-
C.
World War II merchant ship type
A World War II merchant ship type is a standardized class of civilian cargo or transport vessel designed or adapted during the war to efficiently move goods, troops, and supplies under wartime conditions and constraints.
-
D.
World War II cruiser
A World War II cruiser is a fast, medium-sized warship designed for long-range operations, providing fleet screening, surface combat, and shore bombardment using a mix of guns, torpedoes, and later radar-directed fire control.
-
E.
Cold War-era naval vessel
A Cold War-era naval vessel is a warship designed and operated between roughly 1945 and 1991, optimized for anti-submarine warfare, missile engagement, and nuclear deterrence within the geopolitical standoff between NATO and the Warsaw Pact.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:08 p.m.