Triple
T27636094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Light Chelada |
E696471
|
entity |
| Predicate | usesBaseBeer |
P66976
|
FINISHED |
| Object | Bud Light |
—
|
NE NERFINISHED |
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: Bud Light | Statement: [Bud Light Chelada, usesBaseBeer, Bud Light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBaseBeer Context triple: [Bud Light Chelada, usesBaseBeer, Bud Light]
-
A.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
B.
beerBrewedBy
Indicates that a particular beer is produced or created by a specific brewer, brewery, or brewing entity.
-
C.
isMixedBeer
chosen
Indicates that a beer is composed by mixing two or more different beers together.
-
D.
isBavarianBeer
Indicates that something is a beer originating from or characteristic of Bavaria.
-
E.
hasNotableBeer
Indicates that an entity is associated with a beer that is recognized as distinctive, famous, or otherwise noteworthy.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 2:23 p.m.