Triple
T19157676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inmazeb |
E468966
|
entity |
| Predicate | isHumanMonoclonalAntibody |
P134655
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Inmazeb, isHumanMonoclonalAntibody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHumanMonoclonalAntibody Context triple: [Inmazeb, isHumanMonoclonalAntibody, true]
-
A.
antibodyType
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
-
B.
associatedWithAntibody
Indicates a relationship where something is linked or connected to a specific antibody, such as being produced by it, targeted by it, or otherwise functionally related to it.
-
C.
basedOnAntibody
Indicates that something is derived from, developed using, or fundamentally dependent on a specific antibody.
-
D.
impactOnMonoclonalAntibodies
Indicates the effect that something has on the behavior, efficacy, or properties of monoclonal antibodies.
-
E.
isPegylated
Indicates that a molecule, typically a drug or therapeutic agent, has been chemically modified by the attachment of polyethylene glycol (PEG) chains.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeba91a081909c04d61d6117da06 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.