Triple
T5327965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresh Fruit and Vegetable Program |
E123229
|
entity |
| Predicate | nutritionComponent |
P62846
|
FINISHED |
| Object | promotion of whole fruits |
—
|
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: promotion of whole fruits | Statement: [Fresh Fruit and Vegetable Program, nutritionComponent, promotion of whole fruits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nutritionComponent Context triple: [Fresh Fruit and Vegetable Program, nutritionComponent, promotion of whole fruits]
-
A.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
focusesOnNutrition
Indicates that the subject’s primary attention, activity, or content is centered on nutrition-related topics, practices, or goals.
-
C.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
D.
foodCustom
Indicates a culturally specific practice, rule, or tradition related to the preparation, serving, or consumption of food.
-
E.
foodItem
Indicates that one entity is a food item that can be eaten or used as food in relation to another entity.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8593bd6c8190b2054e548ddf2458 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.