Triple
T19066425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey–Nicolaou macrolactonization |
E466669
|
entity |
| Predicate | typicalRingSize |
P134157
|
FINISHED |
| Object | 12- to 30-membered ring |
—
|
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: 12- to 30-membered ring | Statement: [Corey–Nicolaou macrolactonization, typicalRingSize, 12- to 30-membered ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRingSize Context triple: [Corey–Nicolaou macrolactonization, typicalRingSize, 12- to 30-membered ring]
-
A.
ringsOn
Indicates that one entity encircles or forms a ring around another entity, typically by being placed around it.
-
B.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
-
C.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
D.
typicalCaseDiameter
Indicates the usual or standard diameter value associated with an object or case in typical conditions.
-
E.
usesRingStyle
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
- 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.