Triple
T19372536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20 Mule Team Borax |
E484577
|
entity |
| Predicate | chemicalClassification |
P38028
|
FINISHED |
| Object | borate salt |
—
|
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: borate salt | Statement: [20 Mule Team Borax, chemicalClassification, borate salt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalClassification Context triple: [20 Mule Team Borax, chemicalClassification, borate salt]
-
A.
hasChemicalClass
chosen
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
B.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
C.
drugClass
Indicates that one entity is classified as a particular pharmacological or therapeutic category of drugs in relation to another entity.
-
D.
hasPharmacologicClass
Indicates that a drug or medicinal product belongs to a specific pharmacologic class based on its mechanism of action or therapeutic effect.
-
E.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619b1b5fc819089f9fc43f407bbb0 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.