Triple
T4231877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brassicaceae |
E94597
|
entity |
| Predicate | containsAllergen |
P23191
|
FINISHED |
| Object | mustard allergens |
—
|
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: mustard allergens | Statement: [Brassicaceae, containsAllergen, mustard allergens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAllergen Context triple: [Brassicaceae, containsAllergen, mustard allergens]
-
A.
containsAllergenicCompound
chosen
Indicates that the subject entity includes one or more compounds known to cause allergic reactions.
-
B.
containsEggs
Indicates that something includes eggs as one of its components or ingredients.
-
C.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
D.
traditionallyBelievedToContain
Indicates that something is customarily or historically thought to include or hold something else, regardless of whether this belief is factually accurate.
-
E.
notableAllergenicGenera
Indicates that the subject is associated with genera that are particularly notable for causing allergic reactions.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e642aac8190977dd101e27afcbb |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.