Triple
T27729869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Punch |
E697400
|
entity |
| Predicate | energyDrinkStyle |
P68535
|
FINISHED |
| Object | punch-style |
—
|
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: punch-style | Statement: [Pacific Punch, energyDrinkStyle, punch-style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyDrinkStyle Context triple: [Pacific Punch, energyDrinkStyle, punch-style]
-
A.
isSoftDrinkVariantOf
Indicates that one soft drink is a specific version, flavor, or formulation derived from or based on another soft drink.
-
B.
cocktailStyle
Indicates that one entity is characterized by, prepared in, or associated with the cocktail style of another entity.
-
C.
beverageSubcategory
chosen
Indicates a more specific classification within a broader beverage category, defining the subtype or subcategory of a drink.
-
D.
signatureDrink
Indicates that a particular drink is the characteristic or specially associated beverage of an entity (such as a person, venue, or brand).
-
E.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 3:11 p.m.