Triple
T9917608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busch beer |
E185908
|
entity |
| Predicate | calorieProfile |
P91144
|
FINISHED |
| Object | relatively low calorie for a regular beer |
—
|
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: relatively low calorie for a regular beer | Statement: [Busch beer, calorieProfile, relatively low calorie for a regular beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calorieProfile Context triple: [Busch beer, calorieProfile, relatively low calorie for a regular beer]
-
A.
hasCalories
Indicates that an entity contains a specified amount of caloric energy.
-
B.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
C.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
D.
nutritionStandard
Indicates that something complies with, or is evaluated against, a defined set of nutritional guidelines or requirements.
-
E.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5673f108190914e0c172dddc65f |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:42 p.m.