Triple
T16418984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschenmoser sulfide contraction |
E398761
|
entity |
| Predicate | involvesBondChange |
P122495
|
FINISHED |
| Object | C–S bond cleavage |
—
|
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: C–S bond cleavage | Statement: [Eschenmoser sulfide contraction, involvesBondChange, C–S bond cleavage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBondChange Context triple: [Eschenmoser sulfide contraction, involvesBondChange, C–S bond cleavage]
-
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.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
D.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
E.
bondBroken
chosen
Indicates that a previously existing bond or connection between entities has been severed or is no longer intact.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3287a3d348190831b12101d8449b6 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.