Triple
T19157654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inmazeb |
E468966
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | atoltivimab |
—
|
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: atoltivimab | Statement: [Inmazeb, hasComponent, atoltivimab]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: atoltivimab Context triple: [Inmazeb, hasComponent, atoltivimab]
-
A.
ansuvimab
Ansuvimab is a monoclonal antibody used as a therapeutic treatment for infection caused by Zaire ebolavirus (Ebola virus).
-
B.
odesivimab
Odesivimab is a monoclonal antibody used as part of an antibody cocktail therapy for the treatment of Ebola virus infection.
-
C.
Inmazeb (in combination with atoltivimab and odesivimab)
Inmazeb is an FDA-approved antibody cocktail therapy used to treat infections caused by Zaire ebolavirus.
-
D.
maftivimab
chosen
Maftivimab is a monoclonal antibody used as part of an antibody cocktail therapy for the treatment of Ebola virus infection.
-
E.
Ofatumumab
Ofatumumab is a fully human monoclonal antibody used primarily in the treatment of certain B‑cell malignancies and relapsing forms of multiple sclerosis.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 12:06 p.m.