Triple
T28531234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milk |
E722046
|
entity |
| Predicate | energyPer100g |
P51659
|
FINISHED |
| Object | Approximately 60–70 kcal for whole cow milk |
—
|
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 60–70 kcal for whole cow milk | Statement: [Milk, energyPer100g, Approximately 60–70 kcal for whole cow milk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyPer100g Context triple: [Milk, energyPer100g, Approximately 60–70 kcal for whole cow milk]
-
A.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
B.
hasNutrientContent
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
-
C.
hasCalories
chosen
Indicates that an entity contains a specified amount of caloric energy.
-
D.
energyDensityByVolume
Indicates the amount of energy contained per unit of volume in a given system or material.
-
E.
typicalFatContent
Indicates the usual or characteristic amount of fat contained in something, such as a food or product.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 3:28 a.m.