Triple
T6899280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People Make Glasgow |
E159451
|
entity |
| Predicate | brandingApproach |
P74011
|
FINISHED |
| Object | people-centred branding |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: people-centred branding | Statement: [People Make Glasgow, brandingApproach, people-centred branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandingApproach Context triple: [People Make Glasgow, brandingApproach, people-centred branding]
-
A.
brandingNote
Indicates that an entity has an associated note or comment specifically about its branding, such as style, usage, or presentation guidelines.
-
B.
brandingGoal
Indicates the strategic objective or desired outcome that an entity aims to achieve through its branding efforts.
-
C.
brandingMeaning
Indicates the conceptual message, values, or identity that a brand is intended to convey or represent.
-
D.
brandingScope
Indicates the extent or range within which a particular brand identity, strategy, or elements are applied or recognized.
-
E.
brandingFeature
Indicates that one entity serves as a branding-related characteristic, element, or attribute that helps define or distinguish another entity’s brand identity.
- F. None of above. chosen
Provenance (4 batches)
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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95f26a08190ac9a5068433ef603 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.