Triple
T23399907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blood–brain barrier |
E559473
|
entity |
| Predicate | permitsPassageOf |
P11437
|
FINISHED |
| Object | small lipophilic molecules |
—
|
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: small lipophilic molecules | Statement: [blood–brain barrier, permitsPassageOf, small lipophilic molecules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsPassageOf Context triple: [blood–brain barrier, permitsPassageOf, small lipophilic molecules]
-
A.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
B.
canPass
chosen
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
C.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
D.
passesThroughArea
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dedfcc8190ab93cec3c3d15c53 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.