Triple
T26794627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre Hotels Group |
E670610
|
entity |
| Predicate | notableBrandTiering |
P93352
|
FINISHED |
| Object | budget to upscale range |
—
|
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: budget to upscale range | Statement: [Louvre Hotels Group, notableBrandTiering, budget to upscale range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBrandTiering Context triple: [Louvre Hotels Group, notableBrandTiering, budget to upscale range]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
brandLevel
chosen
Indicates the hierarchical rank or tier of a brand within a defined brand structure or classification system.
-
C.
popularBrand
Indicates that a brand is widely liked, recognized, or frequently chosen by many people.
-
D.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
E.
brandScale
Indicates the extent or level of a brand’s size, reach, or influence within its market or context.
- F. None of above.
Provenance (3 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 27, 2026, 4:18 a.m.