Triple
T27636128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Light Chelada |
E696471
|
entity |
| Predicate | intendedConsumption |
P174255
|
FINISHED |
| Object | casual drinking |
—
|
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: casual drinking | Statement: [Bud Light Chelada, intendedConsumption, casual drinking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedConsumption Context triple: [Bud Light Chelada, intendedConsumption, casual drinking]
-
A.
intendedIntake
Indicates the amount or type of something (such as a substance, nutrient, or resource) that is planned or prescribed to be taken in by an entity.
-
B.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
C.
consumptionState
Indicates the current status or condition of how something is being used up, consumed, or depleted.
-
D.
consumptionMethod
Indicates the manner or process by which something is consumed, used up, or ingested.
-
E.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 27, 2026, 2:24 p.m.