Triple
T32996880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHG Hotels & Resorts |
E844254
|
entity |
| Predicate | hasBrandPortfolioRange |
P181690
|
FINISHED |
| Object | luxury hotels |
—
|
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: luxury hotels | Statement: [IHG Hotels & Resorts, hasBrandPortfolioRange, luxury hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandPortfolioRange Context triple: [IHG Hotels & Resorts, hasBrandPortfolioRange, luxury hotels]
-
A.
partOfBrandPortfolioOf
Indicates that one brand is included within, and belongs to, the overall brand portfolio of another entity.
-
B.
ownsBrandPortfolio
Indicates that one entity possesses and controls a collection of brands as part of its brand portfolio.
-
C.
hasBrandArchitecture
Indicates that one entity defines, structures, or governs the brand architecture (the organized system of brands, sub-brands, and their relationships) of another entity.
-
D.
isBrandFamilyOf
Indicates that one brand belongs to, or is part of, a broader brand family or umbrella brand.
-
E.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 1, 2026, 1:22 a.m.