Triple
T23399624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bapineuzumab |
E559467
|
entity |
| Predicate | hasEpitope |
P37224
|
FINISHED |
| Object | N-terminus of amyloid beta |
—
|
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: N-terminus of amyloid beta | Statement: [bapineuzumab, hasEpitope, N-terminus of amyloid beta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpitope Context triple: [bapineuzumab, hasEpitope, N-terminus of amyloid beta]
-
A.
hasEpitomeBy
Indicates that something is represented, summarized, or exemplified by a particular epitome (a concise or quintessential representation of it).
-
B.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
C.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
D.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
-
E.
hasProteinBinding
chosen
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
- 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.