Triple
T16418966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschenmoser sulfide contraction |
E398761
|
entity |
| Predicate | usesIntermediate |
P25490
|
FINISHED |
| Object | thioamide |
—
|
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: thioamide | Statement: [Eschenmoser sulfide contraction, usesIntermediate, thioamide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIntermediate Context triple: [Eschenmoser sulfide contraction, usesIntermediate, thioamide]
-
A.
hasIntermediate
Indicates that there exists one or more entities that serve as a middle or transitional step between two related entities or stages.
-
B.
usesIntermediateRepresentation
Indicates that one entity performs its processing or communication by first converting information into an intermediate representation before reaching the final form or outcome.
-
C.
usesIntermediateSlope
Indicates that an entity employs or operates on a slope of intermediate steepness as part of its process or behavior.
-
D.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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.