Triple
T10188262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PQ convoys |
E236966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II convoy series |
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: World War II convoy series Context triple: [PQ convoys, instanceOf, World War II convoy series]
-
A.
World War II supply line
A World War II supply line is the network of transportation routes, logistics operations, and support infrastructure used to move troops, equipment, fuel, and provisions to and from battlefronts during the war.
-
B.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
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 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 project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:12 p.m.