Triple
T17939120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemanta |
E448541
|
entity |
| Predicate | dietaryRecommendationInAyurveda |
P95772
|
FINISHED |
| Object | nourishing and warming foods |
—
|
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: nourishing and warming foods | Statement: [Hemanta, dietaryRecommendationInAyurveda, nourishing and warming foods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryRecommendationInAyurveda Context triple: [Hemanta, dietaryRecommendationInAyurveda, nourishing and warming foods]
-
A.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
dietAdvocated
chosen
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.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
E.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9455fc81908bf595f9ed42c624 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.