Triple
T36374174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shredded Wheat |
E895851
|
entity |
| Predicate | doesNotTypicallyContain |
P1817
|
FINISHED |
| Object | artificial flavors |
—
|
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: artificial flavors | Statement: [Shredded Wheat, doesNotTypicallyContain, artificial flavors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotTypicallyContain Context triple: [Shredded Wheat, doesNotTypicallyContain, artificial flavors]
-
A.
doesNotPrimarilyContain
Indicates that one entity does not have another entity as its main or predominant component, element, or content.
-
B.
doesNotHave
chosen
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
C.
doesNotTreat
Indicates that one entity refrains from or fails to provide treatment or care to another entity.
-
D.
doesNotServe
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
E.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.