Triple
T14008595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moderna |
E337017
|
entity |
| Predicate | usesDeliverySystem |
P34915
|
FINISHED |
| Object | lipid nanoparticles |
—
|
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: lipid nanoparticles | Statement: [Moderna, usesDeliverySystem, lipid nanoparticles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDeliverySystem Context triple: [Moderna, usesDeliverySystem, lipid nanoparticles]
-
A.
deliverySystem
chosen
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
B.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
C.
offersDeliveryTo
Indicates that one entity provides delivery services to another entity or location.
-
D.
ballDeliveryMethod
Indicates the manner or technique by which a ball is delivered, passed, or thrown from one entity to another.
-
E.
deliveryPlatform
Indicates that one entity serves as the platform, service, or medium through which another entity’s delivery or distribution is carried out.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed44f90819099ad08c09c066b56 |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.