Triple
T23573177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noyori asymmetric hydrogenation catalysts |
E580172
|
entity |
| Predicate | solventCompatibility |
P79103
|
FINISHED |
| Object | polar protic solvents |
—
|
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: polar protic solvents | Statement: [Noyori asymmetric hydrogenation catalysts, solventCompatibility, polar protic solvents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solventCompatibility Context triple: [Noyori asymmetric hydrogenation catalysts, solventCompatibility, polar protic solvents]
-
A.
typicalSolvent
chosen
Indicates that one entity is commonly or characteristically used as a solvent for the other entity.
-
B.
canDissolveWith
Indicates that one substance is capable of dissolving another substance when they are combined.
-
C.
canBeDissolvedWith
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
D.
solubilityInWater
Indicates how readily a substance dissolves in water under specified conditions.
-
E.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd40c9c8190b666a2010d723bf1 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.