Triple
T31535617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | entacapone |
E804592
|
entity |
| Predicate | doesNotCross |
P171939
|
FINISHED |
| Object | blood–brain barrier effectively |
—
|
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 effectively | Statement: [entacapone, doesNotCross, blood–brain barrier effectively]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotCross Context triple: [entacapone, doesNotCross, blood–brain barrier effectively]
-
A.
notCrossing
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
B.
doesNotCrossOrbitOf
Indicates that the path or trajectory of one entity never intersects or passes through the orbital path of another entity.
-
C.
cannotBeCrossedBy
Indicates that one entity forms a barrier or obstacle that another entity is unable to pass through or traverse.
-
D.
doesNotInterlineWith
Indicates that two elements, such as routes or services, do not share a common segment or coordinated connection for through-service or transfer.
-
E.
notCoterminousWith
Indicates that two entities do not share the same boundaries in space, time, or extent and therefore are not exactly coincident.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:03 p.m.