Triple
T27211082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stork enamine reaction |
E683997
|
entity |
| Predicate | workup |
P162256
|
FINISHED |
| Object | aqueous acid hydrolysis |
—
|
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: aqueous acid hydrolysis | Statement: [Stork enamine reaction, workup, aqueous acid hydrolysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workup Context triple: [Stork enamine reaction, workup, aqueous acid hydrolysis]
-
A.
diagnoses
Indicates that a medical professional identifies and determines the nature or cause of a condition, disease, or problem in a patient.
-
B.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
C.
resultOfInvestigation
Indicates that something (such as a finding, conclusion, or outcome) is produced or determined as the consequence of an investigation.
-
D.
works in
Indicates that one entity performs their job or professional activities within the organization, location, or context represented by another entity.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62619146c8190a2c37c7c6b105edc |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:39 a.m.