Triple
T22507217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mathematical-Mechanical Institute in Munich |
E556419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | optical instrument workshop |
C46420
|
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: optical instrument workshop Context triple: [Mathematical-Mechanical Institute in Munich, instanceOf, optical instrument workshop]
-
A.
optical instrument
An optical instrument is a device that uses lenses, mirrors, or other optical components to manipulate light in order to enhance, analyze, or capture visual information.
-
B.
optics company
An optics company is a business that designs, manufactures, and/or distributes optical products and technologies such as lenses, optical instruments, imaging systems, and related components for various applications.
-
C.
optical engineer
An optical engineer is a professional who designs, analyzes, and optimizes systems and devices that manipulate light, such as lenses, lasers, imaging systems, and fiber-optic components, for applications in fields like telecommunications, medicine, manufacturing, and consumer electronics.
-
D.
optical component
An optical component is a physical element designed to manipulate light—such as by transmitting, reflecting, refracting, focusing, or filtering it—within an optical system.
-
E.
optics research center
An optics research center is a specialized facility dedicated to advancing the science and technology of light and optical systems through experimental, theoretical, and applied research.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.