Triple
T25637529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona Light |
E642746
|
entity |
| Predicate | isLowerCalorieVersionOf |
P148690
|
FINISHED |
| Object | Corona Extra |
—
|
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: Corona Extra | Statement: [Corona Light, isLowerCalorieVersionOf, Corona Extra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowerCalorieVersionOf Context triple: [Corona Light, isLowerCalorieVersionOf, Corona Extra]
-
A.
calorieLevel
Indicates the relationship between an entity and the amount of calories it contains or provides, typically categorized by intensity or range (e.g., low, medium, high).
-
B.
isLowCalorieBeer
chosen
Indicates that a beer has a relatively low calorie content compared to typical beers.
-
C.
hasSodiumContentReductionComparedToOriginal
Indicates that the sodium content of one item is reduced relative to that of its original or reference version.
-
D.
isFlavouredVariantOf
Indicates that one item is a version of another that has been modified or distinguished specifically by added or altered flavor characteristics.
-
E.
hasCalories
Indicates that an entity contains a specified amount of caloric energy.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:34 p.m.