Triple
T18288579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schrock carbene |
E438047
|
entity |
| Predicate | hasCarbeneCarbonCharge |
P8394
|
FINISHED |
| Object | formally negative |
—
|
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: formally negative | Statement: [Schrock carbene, hasCarbeneCarbonCharge, formally negative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarbeneCarbonCharge Context triple: [Schrock carbene, hasCarbeneCarbonCharge, formally negative]
-
A.
hasCation
Indicates that something contains, is associated with, or involves a positively charged ion (cation) in its composition or structure.
-
B.
hasChargeConjugation
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
C.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
hasChiralCenters
Indicates that a molecule possesses one or more chiral (stereogenic) centers, leading to possible stereoisomerism.
-
E.
hasCharge
chosen
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
- 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.