Triple
T37698144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotels.com |
E938983
|
entity |
| Predicate | websiteLanguageSupport |
P56949
|
FINISHED |
| Object | multiple languages |
—
|
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: multiple languages | Statement: [Hotels.com, websiteLanguageSupport, multiple languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: websiteLanguageSupport Context triple: [Hotels.com, websiteLanguageSupport, multiple languages]
-
A.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
-
B.
hasCustomerServiceLanguage
Indicates that an entity provides customer service in a specified language or set of languages.
-
C.
serviceBrandLanguage
chosen
Indicates the language or languages in which a service brand communicates or is presented.
-
D.
isSupportedByLanguage
Indicates that something (such as a feature, format, or construct) is compatible with and can be handled or recognized by a particular language.
-
E.
languageOfSupportMaterials
Indicates the language in which support or help materials are provided or made available.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.