Triple
T32136155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgur |
E820767
|
entity |
| Predicate | glycemicIndex |
P99243
|
FINISHED |
| Object | relatively low |
—
|
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: relatively low | Statement: [Bulgur, glycemicIndex, relatively low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glycemicIndex Context triple: [Bulgur, glycemicIndex, relatively low]
-
A.
hasPrimaryCarbohydrate
Indicates that one entity has another entity as its main or principal carbohydrate component.
-
B.
isGlutenFree
Indicates that something does not contain gluten and is suitable for individuals avoiding gluten in their diet.
-
C.
calorieLevel
chosen
Indicates the relationship between an entity and the amount of calories it contains or provides, typically categorized by intensity or range (e.g., low, medium, high).
-
D.
isBrittle
Indicates that an entity has a tendency to break, crack, or shatter easily when subjected to stress or force, rather than deforming.
-
E.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9a9bc4c8190a88918fc4f91136a |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.