Triple
T21021887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpringHill Suites by Marriott at Carowinds |
E517829
|
entity |
| Predicate | cateredActivity |
P29202
|
FINISHED |
| Object | leisure travel |
—
|
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: leisure travel | Statement: [SpringHill Suites by Marriott at Carowinds, cateredActivity, leisure travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateredActivity Context triple: [SpringHill Suites by Marriott at Carowinds, cateredActivity, leisure travel]
-
A.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
B.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
C.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
D.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
E.
servesEventType
chosen
Indicates that an entity provides or supports a particular type or category of event.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5db0b88190ae61ea8b38e8ecf7 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.