Triple
T12038003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaccines for Adults program |
E286588
|
entity |
| Predicate | mayIncludeVaccineType |
P53912
|
FINISHED |
| Object | influenza vaccine |
—
|
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: influenza vaccine | Statement: [Vaccines for Adults program, mayIncludeVaccineType, influenza vaccine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeVaccineType Context triple: [Vaccines for Adults program, mayIncludeVaccineType, influenza vaccine]
-
A.
vaccineUsed
Indicates that a particular vaccine has been administered or applied in a given medical or experimental context.
-
B.
covid19VaccineType
Indicates the specific type or category of COVID-19 vaccine associated with an entity.
-
C.
encodesInVaccines
Indicates that one entity (such as genetic material or information) is incorporated into or represented within the formulation of a vaccine.
-
D.
hasVaccine
Indicates that one entity possesses, provides, or is associated with a specific vaccine in relation to another entity.
-
E.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.