Triple
T6854559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goya champuru |
E158104
|
entity |
| Predicate | nutritionalAspect |
P3602
|
FINISHED |
| Object | rich in vitamins from bitter melon |
—
|
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: rich in vitamins from bitter melon | Statement: [Goya champuru, nutritionalAspect, rich in vitamins from bitter melon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nutritionalAspect Context triple: [Goya champuru, nutritionalAspect, rich in vitamins from bitter melon]
-
A.
nutritionType
chosen
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
C.
focusesOnNutrition
Indicates that the subject’s primary attention, activity, or content is centered on nutrition-related topics, practices, or goals.
-
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.
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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d851321481908c49c2c949359703 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.