Triple
T4111066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISOTYPE visual communication system |
E88572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | visual communication system |
C11445
|
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 communication system Context triple: [ISOTYPE visual communication system, instanceOf, visual communication system]
-
A.
signage system
A signage system is an organized set of visual elements and standards used to guide, inform, and direct people within physical or digital environments.
-
B.
visual modeling language
A visual modeling language is a formal system that uses graphical notations (such as diagrams, symbols, and connectors) to represent, design, and communicate the structure and behavior of complex systems.
-
C.
iconographic program
An iconographic program is a deliberately organized set of visual images and symbols, often in a specific spatial arrangement, designed to convey a coherent narrative, theological message, or ideological theme.
-
D.
visual certification company
A visual certification company is an organization that evaluates, verifies, and officially certifies the authenticity, quality, or compliance of visual content, designs, or visual-based products according to defined standards.
-
E.
government visual identity system
chosen
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.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:41 p.m.