Triple
T20301422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaxzevria COVID-19 vaccine |
E505486
|
entity |
| Predicate | wasFirstUsedIn |
P81076
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Vaxzevria COVID-19 vaccine, wasFirstUsedIn, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstUsedIn Context triple: [Vaxzevria COVID-19 vaccine, wasFirstUsedIn, 2020]
-
A.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
B.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
C.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
-
D.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
E.
firstMajorUseYear
chosen
Indicates the calendar year in which something was first put into major or primary use.
- 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_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. |
Created at: April 16, 2026, 11:17 a.m.