Triple
T13817126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thallium |
E332046
|
entity |
| Predicate | commonCompound |
P111610
|
FINISHED |
| Object | thallium(I) sulfate |
—
|
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: thallium(I) sulfate | Statement: [thallium, commonCompound, thallium(I) sulfate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCompound Context triple: [thallium, commonCompound, thallium(I) sulfate]
-
A.
commonCompoundNameElement
Indicates that two chemical compound names share a common structural or naming element within their nomenclature.
-
B.
commonIon
Indicates that two substances share at least one identical ion in solution, linking them through the common ion effect.
-
C.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
- F. None of above. chosen
Provenance (4 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0281bb988190803ee195f430b9c8 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.