Triple
T31818446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNT162b2 |
E812198
|
entity |
| Predicate | hasPrimaryInjectionSite |
P202526
|
FINISHED |
| Object | deltoid muscle |
—
|
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: deltoid muscle | Statement: [BNT162b2, hasPrimaryInjectionSite, deltoid muscle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryInjectionSite Context triple: [BNT162b2, hasPrimaryInjectionSite, deltoid muscle]
-
A.
hasTypicalLesionSite
Indicates that a disease or condition is characteristically associated with lesions occurring at a particular anatomical site.
-
B.
hasPrimaryAccessShaft
Indicates that one entity serves as the main access shaft associated with another entity.
-
C.
treatsAnatomicalSite
Indicates that an action, intervention, or agent is directed toward and intended to treat a specific anatomical site.
-
D.
suspectedTestSite
Indicates that a location or facility is believed or suspected to be a site where tests or experiments are conducted.
-
E.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_6a008d5fe63c8190ab4f5a31c249c674 |
completed | May 10, 2026, 1:51 p.m. |
Created at: April 30, 2026, 11:45 p.m.