Triple
T16418992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschenmoser sulfide contraction |
E398761
|
entity |
| Predicate | hasKeyStep |
P123359
|
FINISHED |
| Object | rearrangement of sulfur-stabilized intermediate |
—
|
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: rearrangement of sulfur-stabilized intermediate | Statement: [Eschenmoser sulfide contraction, hasKeyStep, rearrangement of sulfur-stabilized intermediate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyStep Context triple: [Eschenmoser sulfide contraction, hasKeyStep, rearrangement of sulfur-stabilized intermediate]
-
A.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
-
C.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
D.
hasKeyPhase
Indicates that an entity possesses or is associated with a specific key phase within a process, lifecycle, or sequence.
-
E.
hasKeyResult
Indicates that an entity is associated with a specific key result it aims to achieve or is responsible for.
- 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_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. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.