Triple
T11467517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otl Aicher’s pictogram system for Munich 1972 |
E271815
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | visual identity component |
C28851
|
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: visual identity component Context triple: [Otl Aicher’s pictogram system for Munich 1972, instanceOf, visual identity component]
-
A.
corporate identity element
A corporate identity element is any visual, verbal, or symbolic component (such as a logo, color scheme, or tagline) that consistently represents and distinguishes an organization’s brand.
-
B.
university visual identity element
A university visual identity element is a standardized graphic component—such as a logo, seal, wordmark, color, or typeface—used consistently to represent and distinguish the institution across all communications and materials.
-
C.
government visual identity system
A government visual identity system is a standardized set of design elements—such as logos, colors, typography, and layout rules—that consistently represent a government’s authority, values, and services across all communications and media.
-
D.
design system
chosen
A design system is a structured collection of reusable components, patterns, and guidelines that ensures visual and functional consistency across a product or suite of products.
-
E.
logo designer
A logo designer is a creative professional who conceptualizes and crafts distinctive visual symbols and wordmarks that represent and communicate a brand’s identity, values, and personality.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:35 p.m.