Triple
T12744642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedestal Convoy |
E304574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied naval operation |
C27249
|
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: Allied naval operation Context triple: [Pedestal Convoy, instanceOf, Allied naval operation]
-
A.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
-
B.
Kriegsmarine operation
A Kriegsmarine operation is a coordinated naval action planned and executed by Nazi Germany’s navy during World War II to achieve specific military, strategic, or logistical objectives at sea.
-
C.
U.S. Navy operation
A U.S. Navy operation is a coordinated maritime, air, cyber, and/or land activity conducted by the United States Navy to achieve specific military, security, or humanitarian objectives under defined rules of engagement and command structures.
-
D.
World War II commando raid
A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
-
E.
World War II convoy series
chosen
A World War II convoy series is a sequence of organized Allied or Axis merchant and naval ship movements, typically identified by a code, that traveled together under escort for mutual protection against enemy attacks during the war.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.