Triple
T4360519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevin Boys |
E98649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II home front workforce |
C15797
|
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 home front workforce Context triple: [Bevin Boys, instanceOf, World War II home front workforce]
-
A.
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.
-
B.
war economy
A war economy is an economic system in which a nation’s resources, production, and policies are heavily directed toward supporting military conflict, often involving central planning, rationing, and reallocation of labor and capital from civilian to defense needs.
-
C.
theater of World War II
The theater of World War II is a conceptual class representing a distinct geographic region and operational context in which military campaigns, battles, and strategic activities of the war were planned, conducted, and coordinated.
-
D.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
E.
World War II-era agency
A World War II-era agency is an organization, typically governmental or intergovernmental, established during the Second World War to coordinate military, economic, intelligence, or civilian efforts in support of the war.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:16 p.m.