Triple
T20301087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagrisso |
E505479
|
entity |
| Predicate | canPenetrate |
P11437
|
FINISHED |
| Object | blood–brain barrier |
—
|
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: blood–brain barrier | Statement: [Tagrisso, canPenetrate, blood–brain barrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPenetrate Context triple: [Tagrisso, canPenetrate, blood–brain barrier]
-
A.
canPass
chosen
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
B.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
C.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
-
D.
hasPenetrance
Indicates that a particular genetic variant or factor is expressed as a trait or condition in a specified proportion of individuals who carry it.
-
E.
canBreakBlocks
Indicates that an entity has the ability to destroy or remove blocks within the environment.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770c700c81909da247cef0d0f1eb |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:17 a.m.