Triple
T32357614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autograph Collection |
E826776
|
entity |
| Predicate | amenityProfile |
P157271
|
FINISHED |
| Object | full-service 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: full-service hotels | Statement: [Autograph Collection, amenityProfile, full-service hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amenityProfile Context triple: [Autograph Collection, amenityProfile, full-service hotels]
-
A.
amenityContext
Indicates the situational or environmental setting in which an amenity is provided, used, or relevant.
-
B.
amenityScope
chosen
Indicates the range or extent of services, facilities, or conveniences that an amenity provides or applies to.
-
C.
architectureProfile
Indicates the structural or organizational design characteristics that define how a system, product, or entity is built or arranged.
-
D.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
E.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9029508190b3e33e5dd44cf489 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:49 a.m.