Triple
T19066422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey–Nicolaou macrolactonization |
E466669
|
entity |
| Predicate | bondsFormed |
P134155
|
FINISHED |
| Object | lactone C–O bond |
—
|
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: lactone C–O bond | Statement: [Corey–Nicolaou macrolactonization, bondsFormed, lactone C–O bond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondsFormed Context triple: [Corey–Nicolaou macrolactonization, bondsFormed, lactone C–O bond]
-
A.
involvesForceBond
Indicates a relationship in which two or more entities are connected through a special Force-based bond that links their sensations, emotions, or abilities.
-
B.
numberOfBasesInvolved
Indicates the count of distinct bases or locations that participate in a given event, operation, or relationship.
-
C.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
D.
areFormedAt
Indicates that entities come into existence, are created, or take shape at a specific location, time, or context.
-
E.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e198621481908618f65dd01746fc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:03 p.m.