Triple
T26762377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Cambridge identity |
E674839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institutional identity |
C33819
|
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: institutional identity Context triple: [University of Cambridge identity, instanceOf, institutional identity]
-
A.
corporate identity
Corporate identity is the cohesive visual and conceptual representation of a company—encompassing its logo, design system, messaging, and values—that shapes how it is perceived by internal and external audiences.
-
B.
institutional insignia
chosen
Institutional insignia are official symbols or emblems that visually represent and distinguish an organization, conveying its identity, authority, and values.
-
C.
institution code
An institution code is a standardized alphanumeric identifier assigned to a specific organization, such as a bank, school, or research body, to uniquely distinguish it within a given system or network.
-
D.
institutional leadership
Institutional leadership is the practice of guiding and shaping an organization’s vision, culture, and strategic direction to achieve its long-term goals and fulfill its mission within a broader social and regulatory context.
-
E.
corporate identity system
A corporate identity system is a coordinated set of visual and verbal elements—such as logos, colors, typography, and messaging guidelines—that consistently express and reinforce an organization’s brand across all touchpoints.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:58 a.m.