Triple
T37697606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucinex |
E938970
|
entity |
| Predicate | combinationProductContains |
P153040
|
FINISHED |
| Object | dextromethorphan |
—
|
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: dextromethorphan | Statement: [Mucinex, combinationProductContains, dextromethorphan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinationProductContains Context triple: [Mucinex, combinationProductContains, dextromethorphan]
-
A.
coFormulatedWith
Indicates that one entity is formulated together with another as part of the same combined product or composition.
-
B.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
C.
containsAllergenicCompound
Indicates that the subject entity includes one or more compounds known to cause allergic reactions.
-
D.
hasComponentOfFixedDoseCombination
chosen
Indicates that an entity is a constituent component within a fixed-dose combination product, where multiple components are combined in set proportions.
-
E.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.