Triple
T3043895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Ball |
E83395
|
entity |
| Predicate | cateringIncludes |
P44773
|
FINISHED |
| Object | buffet food |
—
|
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: buffet food | Statement: [May Ball, cateringIncludes, buffet food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateringIncludes Context triple: [May Ball, cateringIncludes, buffet food]
-
A.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
B.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
C.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
D.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
E.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
- F. None of above. chosen
Provenance (4 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5ec5988190b8b6c95c743c6d1e |
completed | March 8, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.