Triple
T18288573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schrock carbene |
E438047
|
entity |
| Predicate | hasElectronicCharacter |
P131197
|
FINISHED |
| Object | nucleophilic carbene |
—
|
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: nucleophilic carbene | Statement: [Schrock carbene, hasElectronicCharacter, nucleophilic carbene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicCharacter Context triple: [Schrock carbene, hasElectronicCharacter, nucleophilic carbene]
-
A.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
B.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
C.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
D.
hasDroidCharacter
Indicates that an entity features or includes a character that is a droid.
-
E.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
- 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_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. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.