Triple
T7517944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Hotel Cheyenne |
E177691
|
entity |
| Predicate | cateringOption |
P68068
|
FINISHED |
| Object | breakfast available |
—
|
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: breakfast available | Statement: [Disney Hotel Cheyenne, cateringOption, breakfast available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateringOption Context triple: [Disney Hotel Cheyenne, cateringOption, breakfast available]
-
A.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
B.
hasFoodOption
chosen
Indicates that an entity offers, provides, or includes a particular type of food or dining option.
-
C.
offersBuffet
Indicates that one entity provides a buffet-style service or meal option to another entity.
-
D.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
E.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f6ccc8819080ffd123fdd59a50 |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.