Triple
T32226550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VEGF-B |
E823217
|
entity |
| Predicate | doesNotBindReceptor |
P5366
|
FINISHED |
| Object | VEGFR-2 |
—
|
NE NERFINISHED |
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: VEGFR-2 | Statement: [VEGF-B, doesNotBindReceptor, VEGFR-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotBindReceptor Context triple: [VEGF-B, doesNotBindReceptor, VEGFR-2]
-
A.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
B.
doesNotDirectlyRegulate
Indicates that one entity has no immediate or primary regulatory control or influence over another entity or process.
-
C.
doesNotCoupleTo
chosen
Indicates that one entity does not form a functional or physical coupling or interaction with another entity.
-
D.
doesNotProduce
Indicates that one entity fails to generate, create, or yield another entity or outcome.
-
E.
doesNotParticipateIn
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbcbd31c8190a482a5fd5040410d |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.