Triple
T34606140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | acalabrutinib |
E888598
|
entity |
| Predicate | hasHigherSelectivityThan |
P147421
|
FINISHED |
| Object | ibrutinib |
—
|
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: ibrutinib | Statement: [acalabrutinib, hasHigherSelectivityThan, ibrutinib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherSelectivityThan Context triple: [acalabrutinib, hasHigherSelectivityThan, ibrutinib]
-
A.
isLessSelectiveThan
chosen
Indicates that one entity has a lower degree of selectivity or strictness in its choices or criteria compared to another entity.
-
B.
hasApproximateSelectivityLevel
Indicates that one entity is associated with another entity representing an estimated or non-exact degree of selectivity.
-
C.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
D.
hasLowerPrecedenceThan
Indicates that one item is ranked or ordered with a lower priority or importance compared to another item.
-
E.
isMoreSpecificThan
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 2:03 a.m.