Triple
T8930090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maschinenbau-AG Nürnberg |
E212630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mechanical engineering company |
C136
|
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: mechanical engineering company Context triple: [Maschinenbau-AG Nürnberg, instanceOf, mechanical engineering company]
-
A.
manufacturing company
chosen
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
B.
mechanical engineer
A mechanical engineer is a professional who applies principles of physics, mathematics, and materials science to design, analyze, manufacture, and maintain mechanical systems and devices.
-
C.
mechanical engineering department
A mechanical engineering department is an academic or organizational unit focused on the education, research, and application of principles related to the design, analysis, manufacturing, and maintenance of mechanical systems and devices.
-
D.
engineering firm
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
-
E.
industrial automation company
An industrial automation company designs, develops, and implements control systems, robotics, and software solutions to optimize and automate manufacturing and industrial processes.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.