Triple
T35279907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese military-industrial complex in Manchuria |
E1018906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-directed industrial system |
C52487
|
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: state-directed industrial system Context triple: [Japanese military-industrial complex in Manchuria, instanceOf, state-directed industrial system]
-
A.
industrial system
chosen
An industrial system is an integrated network of machines, processes, people, and control mechanisms designed to transform raw materials and energy into goods or services efficiently and reliably.
-
B.
industrial production system
An industrial production system is an organized arrangement of people, machines, materials, methods, and information designed to efficiently transform inputs into standardized goods or services at scale.
-
C.
state-based system model
A state-based system model represents a system in terms of a finite set of states, the events or conditions that trigger transitions between those states, and the rules governing how the system evolves over time.
-
D.
state-designated system
A state-designated system is an organized structure, program, or network that has been formally identified, authorized, or recognized by a governmental state authority to perform specific functions or services.
-
E.
engineered system
An engineered system is a deliberately designed and organized set of interacting components, processes, and resources created by humans to perform specific functions and achieve defined objectives within given constraints.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.