Triple
T23907742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breslow intermediate in organocatalysis |
E601249
|
entity |
| Predicate | isTransient |
P3981
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Breslow intermediate in organocatalysis, isTransient, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransient Context triple: [Breslow intermediate in organocatalysis, isTransient, true]
-
A.
isTemporary
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
B.
isShortLived
chosen
Indicates that an entity exists or remains in a particular state for only a brief or limited period of time.
-
C.
isTemporaryDesignation
Indicates that a given designation or label is intended to be used only for a limited time and is not the entity’s permanent or final designation.
-
D.
hasTemporaryStation
Indicates that an entity is associated with a station or facility that is intended to be used only for a limited or non-permanent period.
-
E.
isTransitionalBetween
Indicates that something serves as an intermediate or bridging state, form, or phase between two other distinct states, forms, or phases.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce91e6088190b85b534ab361f888 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:37 p.m.