Triple
T19156997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Équateur Province Ebola outbreak |
E468950
|
entity |
| Predicate | vaccinationStrategy |
P134644
|
FINISHED |
| Object | ring vaccination |
—
|
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: ring vaccination | Statement: [2018 Équateur Province Ebola outbreak, vaccinationStrategy, ring vaccination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vaccinationStrategy Context triple: [2018 Équateur Province Ebola outbreak, vaccinationStrategy, ring vaccination]
-
A.
vaccineUsed
Indicates that a particular vaccine has been administered or applied in a given medical or experimental context.
-
B.
vaccineAvailable
Indicates that a vaccine is obtainable or in stock for use or distribution.
-
C.
covid19VaccineType
Indicates the specific type or category of COVID-19 vaccine associated with an entity.
-
D.
encodesInVaccines
Indicates that one entity (such as genetic material or information) is incorporated into or represented within the formulation of a vaccine.
-
E.
developedVaccineFor
Indicates that one entity created or produced a vaccine intended to prevent or protect against a disease or condition associated with another entity.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb9cf9081908b17073755e83554 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.