Triple
T33292568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bortecad |
E852352
|
entity |
| Predicate | hasATCLevel3Class |
P149271
|
FINISHED |
| Object | proteasome inhibitors |
—
|
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: proteasome inhibitors | Statement: [Bortecad, hasATCLevel3Class, proteasome inhibitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasATCLevel3Class Context triple: [Bortecad, hasATCLevel3Class, proteasome inhibitors]
-
A.
hasATCClass
Indicates that a drug or medicinal product is assigned to a specific Anatomical Therapeutic Chemical (ATC) classification category.
-
B.
ATCLevel3
chosen
Indicates a hierarchical classification relationship where an entity is assigned to, or associated with, a third-level category in the ATC (Anatomical Therapeutic Chemical) system.
-
C.
SAELevel
Indicates the level or degree of a subject according to the SAE (e.g., standard, classification, or grading) scale.
-
D.
hasThreeClasses
Indicates that an entity is associated with exactly three distinct classes.
-
E.
hasThirdDivision
Indicates that an entity possesses or is associated with a third-level division or subdivision within a hierarchical structure.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.