Triple
T34312133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cereal Foods and How to Cook Them |
E880478
|
entity |
| Predicate | mentionsIngredientType |
P40800
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Cereal Foods and How to Cook Them, mentionsIngredientType, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsIngredientType Context triple: [Cereal Foods and How to Cook Them, mentionsIngredientType, wheat]
-
A.
ingredientType
chosen
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
B.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
C.
usesIngredientInfluenceFrom
Indicates that one entity incorporates or applies the influence, properties, or effects derived from a particular ingredient in its action or outcome.
-
D.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
E.
hasKeyIngredientAttribute
Indicates that an entity possesses a specific key ingredient as a defining attribute or component.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.