Triple
T35079163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actemium |
E1012385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial engineering company network |
C12036
|
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: industrial engineering company network Context triple: [Actemium, instanceOf, industrial engineering company network]
-
A.
industrial network
An industrial network is a communication infrastructure that connects machines, sensors, controllers, and enterprise systems within industrial environments to enable real-time data exchange, monitoring, and control of production processes.
-
B.
manufacturing network
chosen
A manufacturing network is an interconnected system of facilities, suppliers, technologies, and logistics that collaboratively plan, produce, and distribute goods across multiple locations.
-
C.
network of industrialists
A network of industrialists is an interconnected group of business leaders and owners in industrial sectors who collaborate, share resources, and influence economic and policy decisions.
-
D.
automotive manufacturing network
An automotive manufacturing network is an interconnected system of facilities, suppliers, logistics providers, and assembly plants that collaboratively design, produce, and deliver vehicles and components across regions or globally.
-
E.
industrial engineering department
An industrial engineering department is an academic or organizational unit focused on optimizing complex systems, processes, and resources to improve efficiency, productivity, and quality in industrial and service environments.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.