Triple
T7803645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischer esterification |
E180491
|
entity |
| Predicate | byproductRemovalMethod |
P23060
|
FINISHED |
| Object | azeotropic distillation of water |
—
|
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: azeotropic distillation of water | Statement: [Fischer esterification, byproductRemovalMethod, azeotropic distillation of water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: byproductRemovalMethod Context triple: [Fischer esterification, byproductRemovalMethod, azeotropic distillation of water]
-
A.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
B.
separationMethod
chosen
Indicates the technique or process used to separate one substance, component, or entity from another.
-
C.
purifiedBy
Indicates that something has been cleansed, refined, or made pure through the action or process performed by another agent or method.
-
D.
methodOfDisposal
Indicates the specific way or process by which something is discarded, eliminated, or otherwise gotten rid of.
-
E.
sterilizationMethod
Indicates the technique or procedure used to achieve sterilization in a given 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:34 p.m.