Triple
T10196388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Converse star chevron logo |
E238172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate visual identity element |
C11453
|
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: corporate visual identity element Context triple: [Converse star chevron logo, instanceOf, corporate visual identity element]
-
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.
corporate flag
A corporate flag is a branded banner or standard that visually represents a company's identity, values, and presence, typically displaying its logo, colors, and name.
-
E.
corporate trademark
chosen
A corporate trademark is a legally protected symbol, name, logo, or design that uniquely identifies and distinguishes a company's goods or services from those of others in the marketplace.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:13 p.m.