Triple
T33389117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENSEMBLE |
E854996
|
entity |
| Predicate | relatedVaccineName |
P206446
|
FINISHED |
| Object | Janssen COVID-19 Vaccine |
E49854
|
NE 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: Janssen COVID-19 Vaccine | Statement: [ENSEMBLE, relatedVaccineName, Janssen COVID-19 Vaccine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedVaccineName Context triple: [ENSEMBLE, relatedVaccineName, Janssen COVID-19 Vaccine]
-
A.
vaccineUsed
Indicates that a particular vaccine has been administered or applied in a given medical or experimental context.
-
B.
relatedDrug
Indicates that one drug has a specified relationship or association with another drug, such as interaction, similarity, or therapeutic linkage.
-
C.
covid19VaccineType
Indicates the specific type or category of COVID-19 vaccine associated with an entity.
-
D.
developedVaccineFor
Indicates that one entity created or produced a vaccine intended to prevent or protect against a disease or condition associated with another entity.
-
E.
vaccineTypeUsed
Indicates that a specific type or category of vaccine was administered or employed in a vaccination event or context.
- F. None of above. chosen
Provenance (5 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3595983b348190b8b1ce8b4bd8e48d |
completed | June 19, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:35 a.m.