Triple
T2190737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darzalex |
E49853
|
entity |
| Predicate | canInterfereWith |
P32707
|
FINISHED |
| Object | blood compatibility testing |
—
|
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 compatibility testing | Statement: [Darzalex, canInterfereWith, blood compatibility testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInterfereWith Context triple: [Darzalex, canInterfereWith, blood compatibility testing]
-
A.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
intervenesWhen
Indicates that one entity takes action to interrupt, mediate, or alter the course of another entity’s ongoing situation or process when certain conditions arise.
-
D.
hasNotableIntersection
Indicates that two entities intersect or cross at a point that is considered significant or noteworthy in some context.
-
E.
canImpair
chosen
Indicates that one entity has the potential or ability to weaken, damage, or reduce the normal function, quality, or effectiveness of another entity.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.