Triple
T20301413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaxzevria COVID-19 vaccine |
E505486
|
entity |
| Predicate | hasVaccinePlatform |
P139588
|
FINISHED |
| Object | non-replicating viral vector |
—
|
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: non-replicating viral vector | Statement: [Vaxzevria COVID-19 vaccine, hasVaccinePlatform, non-replicating viral vector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVaccinePlatform Context triple: [Vaxzevria COVID-19 vaccine, hasVaccinePlatform, non-replicating viral vector]
-
A.
hasVaccine
Indicates that one entity possesses, provides, or is associated with a specific vaccine in relation to another entity.
-
B.
hasVaccineInPlot
Indicates that a vaccine is present, used, or plays a role within the context of a specific plot or storyline.
-
C.
vaccineAvailable
Indicates that a vaccine is obtainable or in stock for use or distribution.
-
D.
testedVaccineOn
Indicates that one entity conducted tests or experiments using another entity as the vaccine subject.
-
E.
vaccineUsed
Indicates that a particular vaccine has been administered or applied in a given medical or experimental context.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770c700c81909da247cef0d0f1eb |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:17 a.m.