Triple
T2670980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau of Industry Operations |
E55745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wartime administrative body |
C236
|
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: wartime administrative body Context triple: [Bureau of Industry Operations, instanceOf, wartime administrative body]
-
A.
wartime agency
chosen
A wartime agency is an organization, typically governmental or intergovernmental, established or empowered during armed conflict to coordinate military, economic, and civilian efforts in support of war objectives.
-
B.
Allied occupation body
An Allied occupation body is an administrative authority established by victorious Allied powers to govern, oversee reconstruction, and implement political, economic, and legal reforms in a defeated or occupied territory following conflict.
-
C.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
D.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
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.
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.