Triple
T24652673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochow process |
E610296
|
entity |
| Predicate | usesReactant |
P79100
|
FINISHED |
| Object | methyl 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: methyl chloride | Statement: [Rochow process, usesReactant, methyl chloride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReactant Context triple: [Rochow process, usesReactant, methyl chloride]
-
A.
reactant
chosen
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
-
B.
usedReaction
Indicates that an entity employed or applied a particular reaction (e.g., chemical, biological, or procedural) as part of an action or process.
-
C.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
-
D.
reactionCondition
Indicates the specific conditions (such as temperature, pressure, catalysts, or environment) under which a reaction occurs or is carried out.
-
E.
usesMolecule
Indicates that one entity employs or utilizes a particular molecule in performing an action, process, or function.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.