Triple
T23399642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bapineuzumab |
E559467
|
entity |
| Predicate | biologicType |
P152110
|
FINISHED |
| Object | IgG monoclonal antibody |
—
|
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: IgG monoclonal antibody | Statement: [bapineuzumab, biologicType, IgG monoclonal antibody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biologicType Context triple: [bapineuzumab, biologicType, IgG monoclonal antibody]
-
A.
biologicalOrigin
Indicates that one entity originates from, is derived from, or is produced by a biological source or organism in relation to another entity.
-
B.
tipoDeOrganismo
Indicates that one entity is classified as a specific type or category of organism in relation to another.
-
C.
organismType
Indicates the biological classification or kind of organism that an entity is.
-
D.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
- 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_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. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:37 p.m.