Triple
T25360044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evans aldol reaction |
E635933
|
entity |
| Predicate | usesAuxiliary |
P4791
|
FINISHED |
| Object | chiral N-acyl oxazolidinone |
—
|
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: chiral N-acyl oxazolidinone | Statement: [Evans aldol reaction, usesAuxiliary, chiral N-acyl oxazolidinone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAuxiliary Context triple: [Evans aldol reaction, usesAuxiliary, chiral N-acyl oxazolidinone]
-
A.
auxiliaryTo
Indicates that one entity serves as a supporting or helping element that assists or modifies the primary action or role of another entity.
-
B.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
C.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
E.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0441108190be510b7bf3a22cea |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:36 p.m.