Triple
T479156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pisco sour |
E9126
|
entity |
| Predicate | servingOccasion |
P14787
|
FINISHED |
| Object | festive events |
—
|
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: festive events | Statement: [pisco sour, servingOccasion, festive events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingOccasion Context triple: [pisco sour, servingOccasion, festive events]
-
A.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
B.
displayOccasion
Indicates the event, context, or situation during which something is presented, shown, or made visible.
-
C.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
-
D.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
-
E.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.