Triple
T7426230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Sugarfree |
E171374
|
entity |
| Predicate | hasCaffeineContentPer250ml |
P38318
|
FINISHED |
| Object | approximately 80 mg |
—
|
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: approximately 80 mg | Statement: [Red Bull Sugarfree, hasCaffeineContentPer250ml, approximately 80 mg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaffeineContentPer250ml Context triple: [Red Bull Sugarfree, hasCaffeineContentPer250ml, approximately 80 mg]
-
A.
hasCaffeineContent
chosen
Indicates that one entity (typically a beverage or substance) possesses a specified amount or presence of caffeine.
-
B.
hasCaffeinatedOption
Indicates that something offers or includes at least one option that contains caffeine.
-
C.
hasBeverageCategory
Indicates that an entity is associated with or classified under a particular beverage category.
-
D.
typicalCaffeineSource
Indicates that one entity is a common or characteristic source from which the other entity typically obtains caffeine.
-
E.
hasCaffeineFreeOption
Indicates that something offers an available version or option that does not contain caffeine.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f303eb988190ba9df7946fce1c86 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.