Triple
T7837449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairmont Hotels and Resorts |
E181720
|
entity |
| Predicate | brandAttributes |
P15065
|
FINISHED |
| Object | heritage |
—
|
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: heritage | Statement: [Fairmont Hotels and Resorts, brandAttributes, heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandAttributes Context triple: [Fairmont Hotels and Resorts, brandAttributes, heritage]
-
A.
brandAttribute
chosen
Indicates that a specific attribute or characteristic is associated with, or describes, a particular brand.
-
B.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
C.
brandIncludes
Indicates that a broader brand or brand portfolio encompasses, owns, or contains the specified sub-brand, product line, or branded entity.
-
D.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
E.
fashionCharacteristic
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c203b4819099c039c617628927 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:46 p.m.