Triple
T20802411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFSP |
E512071
|
entity |
| Predicate | mealStandard |
P141865
|
FINISHED |
| Object | must meet USDA nutrition guidelines |
—
|
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: must meet USDA nutrition guidelines | Statement: [SFSP, mealStandard, must meet USDA nutrition guidelines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mealStandard Context triple: [SFSP, mealStandard, must meet USDA nutrition guidelines]
-
A.
commonMealType
Indicates that two entities share the same general category or type of meal (e.g., breakfast, lunch, dinner).
-
B.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
C.
intendedMeal
Indicates that one entity is the meal that another entity plans or expects to eat.
-
D.
intendedFood
Indicates that one entity is the food item that another entity plans or is meant to eat or consume.
-
E.
typicallyEatenAt
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b207c48190a9ca5895bdf85245 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:39 p.m.