Triple
T37706473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysol |
E939210
|
entity |
| Predicate | typicalActiveIngredient |
P184030
|
FINISHED |
| Object | benzalkonium chloride |
—
|
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: benzalkonium chloride | Statement: [Lysol, typicalActiveIngredient, benzalkonium chloride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActiveIngredient Context triple: [Lysol, typicalActiveIngredient, benzalkonium chloride]
-
A.
activeIngredientOf
chosen
Indicates that one entity is the pharmacologically active component contained within or responsible for the primary effect of another entity, such as a drug or product.
-
B.
hasInactiveIngredient
Indicates that one entity contains another entity as a non-active (inactive) component or ingredient.
-
C.
primaryDrug
Indicates that one drug is identified as the main or most important medication in a given treatment, context, or combination relative to other associated drugs.
-
D.
drugGenericName
Indicates that a drug entity is associated with its generic (non-brand) name.
-
E.
featuresDrug
Indicates that something (such as a product, treatment, or context) includes, involves, or prominently uses a particular drug.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.