Triple
T18288591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schrock carbene |
E438047
|
entity |
| Predicate | typicalAncillaryLigands |
P120395
|
FINISHED |
| Object | alkoxides |
—
|
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: alkoxides | Statement: [Schrock carbene, typicalAncillaryLigands, alkoxides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAncillaryLigands Context triple: [Schrock carbene, typicalAncillaryLigands, alkoxides]
-
A.
ligandType
chosen
Indicates the specific kind or category of ligand associated with, or acting upon, an entity in the relationship.
-
B.
ligandFamily
Indicates that one entity is a ligand belonging to the same functional or structural family as another entity.
-
C.
hasAnion
Indicates that one entity possesses, contains, or is associated with another entity functioning as its anion (negatively charged ion).
-
D.
oxidationStates
Indicates the specific oxidation numbers assigned to an element or atom within a chemical species, reflecting its electron loss or gain state in that context.
-
E.
hasTypicalOxidationState
Indicates that an element or species is associated with a commonly observed or characteristic oxidation state under standard or typical conditions.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fc49b88190bd5b562e0a959e9d |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.