Triple
T16542938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Down to Earth Organic & Natural |
E401865
|
entity |
| Predicate | dietaryPolicy |
P34157
|
FINISHED |
| Object | 100% vegetarian |
—
|
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: 100% vegetarian | Statement: [Down to Earth Organic & Natural, dietaryPolicy, 100% vegetarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryPolicy Context triple: [Down to Earth Organic & Natural, dietaryPolicy, 100% vegetarian]
-
A.
dietaryOptions
chosen
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
B.
dietAdvocated
Indicates that one entity promotes, recommends, or supports a particular diet for another entity or audience.
-
C.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
D.
hasDietaryLaw
Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with another entity.
-
E.
hasDiningPolicy
Indicates that an entity enforces or follows a specific set of rules or guidelines related to dining or meal-related activities.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455fab34819086c77ff45b85f5db |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.