Triple
T27791533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nutrilite |
E701093
|
entity |
| Predicate | hasKeyIngredientType |
P40800
|
FINISHED |
| Object | plant-based ingredients |
—
|
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: plant-based ingredients | Statement: [Nutrilite, hasKeyIngredientType, plant-based ingredients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyIngredientType Context triple: [Nutrilite, hasKeyIngredientType, plant-based ingredients]
-
A.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
hasVariantIngredient
Indicates that one ingredient is an alternative or substitute form of another ingredient used in a product or formulation.
-
C.
hasDishType
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
D.
ingredientType
chosen
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
E.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 5:28 p.m.