Triple
T4132124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rVSV-ZEBOV |
E85063
|
entity |
| Predicate | immuneResponseType |
P54031
|
FINISHED |
| Object | humoral immune response |
—
|
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: humoral immune response | Statement: [rVSV-ZEBOV, immuneResponseType, humoral immune response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immuneResponseType Context triple: [rVSV-ZEBOV, immuneResponseType, humoral immune response]
-
A.
antibodyType
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
-
B.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
-
C.
immuneEvasionMechanism
Indicates a mechanism by which an entity avoids, suppresses, or otherwise interferes with detection or elimination by an immune system.
-
D.
typeOfResistance
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
E.
regulatoryResponse
Indicates a reaction, decision, or adjustment made by a regulatory body in response to a particular event, condition, or entity’s behavior.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:42 p.m.