Triple
T18294283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locarno Classification |
E438191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial design classification |
C7799
|
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 design classification Context triple: [Locarno Classification, instanceOf, industrial design classification]
-
A.
industrial design object
An industrial design object is a mass-produced, functional product whose form, materials, and user interaction are intentionally shaped to optimize usability, aesthetics, and manufacturability.
-
B.
industrial design relationship
An industrial design relationship is the collaborative and often contractual connection between designers, manufacturers, and stakeholders that shapes how functional, aesthetic, and user-centered product solutions are conceived, developed, and brought to market.
-
C.
industrial design award
An industrial design award is a formal recognition given to products or designers for outstanding innovation, functionality, aesthetics, and impact in the field of industrial design.
-
D.
goods classification system
chosen
A goods classification system is a structured framework for categorizing products based on shared characteristics, such as type, use, material, or regulatory requirements, to enable consistent identification, management, and analysis.
-
E.
design discipline
A design discipline is a specialized field of practice focused on systematically planning, shaping, and refining products, services, or experiences to meet functional needs and aesthetic, social, or strategic goals.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.