Triple
T16279317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barton–McCombie deoxygenation |
E395221
|
entity |
| Predicate | keyIntermediate |
P122496
|
FINISHED |
| Object | xanthate ester |
—
|
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: xanthate ester | Statement: [Barton–McCombie deoxygenation, keyIntermediate, xanthate ester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyIntermediate Context triple: [Barton–McCombie deoxygenation, keyIntermediate, xanthate ester]
-
A.
keyInterface
Indicates that one entity functions as the primary or main interface through which another entity is accessed or interacted with.
-
B.
keyMaterial
Indicates that an entity serves as cryptographic key material used to secure, encrypt, or authenticate data in a security-related relationship.
-
C.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
D.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
E.
keyImport
Indicates the action or process of bringing an existing cryptographic key into a system or application for use.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24610908c8190921e507dcb4d8250 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.