Triple
T10292305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | human adenovirus serotype 26 |
E241391
|
entity |
| Predicate | immunogenicityProfile |
P54031
|
FINISHED |
| Object | induces strong T-cell responses |
—
|
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: induces strong T-cell responses | Statement: [human adenovirus serotype 26, immunogenicityProfile, induces strong T-cell responses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immunogenicityProfile Context triple: [human adenovirus serotype 26, immunogenicityProfile, induces strong T-cell responses]
-
A.
immuneResponseType
chosen
Indicates the specific kind or category of immune reaction that occurs in response to a particular stimulus or agent.
-
B.
immunity
Indicates that an entity is protected against or not affected by a particular agent, condition, or influence.
-
C.
antibodyType
Indicates the specific class or subtype of an antibody involved in the described relationship or context.
-
D.
vaccineUsed
Indicates that a particular vaccine has been administered or applied in a given medical or experimental context.
-
E.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d35f048190a215493acdf1f718 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.