Triple
T17705003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xfinity Live! Philadelphia |
E441407
|
entity |
| Predicate | cateredEventType |
P29202
|
FINISHED |
| Object | sporting event watch parties |
—
|
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: sporting event watch parties | Statement: [Xfinity Live! Philadelphia, cateredEventType, sporting event watch parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateredEventType Context triple: [Xfinity Live! Philadelphia, cateredEventType, sporting event watch parties]
-
A.
servesEventType
chosen
Indicates that an entity provides or supports a particular type or category of event.
-
B.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
C.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
D.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
E.
typeOfEvent
Indicates that one entity is classified as a specific kind 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47297359481909629c79220e58245 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.