Triple
T20301415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaxzevria COVID-19 vaccine |
E505486
|
entity |
| Predicate | isGeneticMaterialType |
P3604
|
FINISHED |
| Object | DNA |
—
|
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: DNA | Statement: [Vaxzevria COVID-19 vaccine, isGeneticMaterialType, DNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeneticMaterialType Context triple: [Vaxzevria COVID-19 vaccine, isGeneticMaterialType, DNA]
-
A.
geneticMaterial
chosen
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
B.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
geneticElement
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
D.
isMaterialSpecific
Indicates that a relationship, rule, or property applies only to a particular material or set of materials, rather than being generally applicable.
-
E.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
- 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.