Triple
T15733019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchwald–Hartwig amination |
E381391
|
entity |
| Predicate | formsBond |
P33754
|
FINISHED |
| Object | C–N bond |
—
|
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–N bond | Statement: [Buchwald–Hartwig amination, formsBond, C–N bond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBond Context triple: [Buchwald–Hartwig amination, formsBond, C–N bond]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
C.
binding
chosen
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
D.
formedDuoWith
Indicates that two entities joined together to create a duo, typically collaborating or acting as a pair for a shared purpose or activity.
-
E.
associatedFormation
Indicates that one entity is linked or connected to a particular formation, such as a geological, structural, or organizational configuration.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.