Triple
T5997508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspire Brands |
E133508
|
entity |
| Predicate | hasBrandType |
P67912
|
FINISHED |
| Object | quick-service |
—
|
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: quick-service | Statement: [Inspire Brands, hasBrandType, quick-service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandType Context triple: [Inspire Brands, hasBrandType, quick-service]
-
A.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
B.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
D.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
E.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee274e08190b6478c7ae318ae48 |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.