Triple
T27729686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5-hour Energy |
E697397
|
entity |
| Predicate | caffeineContentRange |
P38318
|
FINISHED |
| Object | about 200 mg per bottle |
—
|
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: about 200 mg per bottle | Statement: [5-hour Energy, caffeineContentRange, about 200 mg per bottle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caffeineContentRange Context triple: [5-hour Energy, caffeineContentRange, about 200 mg per bottle]
-
A.
hasCaffeineContent
chosen
Indicates that one entity (typically a beverage or substance) possesses a specified amount or presence of caffeine.
-
B.
typicalCaffeineSource
Indicates that one entity is a common or characteristic source from which the other entity typically obtains caffeine.
-
C.
hasCaffeinatedOption
Indicates that something offers or includes at least one option that contains caffeine.
-
D.
bottlingStrengthRange
Indicates the range of alcohol strengths at which a beverage is bottled.
-
E.
coffeeOrganization
Indicates a relationship where an organization is involved with coffee, such as producing, distributing, selling, or promoting it.
- 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_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:11 p.m.