Triple
T19454622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggo waffles |
E486702
|
entity |
| Predicate | mayContainAllergen |
P23191
|
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: [Eggo waffles, mayContainAllergen, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayContainAllergen Context triple: [Eggo waffles, mayContainAllergen, wheat]
-
A.
isAllergenFor
Indicates that one entity acts as an allergen that can trigger an allergic reaction in another entity.
-
B.
containsAllergenicCompound
chosen
Indicates that the subject entity includes one or more compounds known to cause allergic reactions.
-
C.
mayBeGlutenFreeIf
Indicates that something has the potential to be gluten-free under certain conditions or assumptions.
-
D.
isNonAllergenic
Indicates that something does not cause allergic reactions or is free from common allergens.
-
E.
actualAllergenComparison
Indicates a comparison between the actual allergen associated with one entity and the allergen associated with another entity, typically to determine if they match, differ, or how they relate.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c117ac8190a38c01c3191beaea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.