Triple
T19773000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prevnar 13 |
E474933
|
entity |
| Predicate | administeredByRoute |
P39634
|
FINISHED |
| Object | intramuscular injection |
—
|
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: intramuscular injection | Statement: [Prevnar 13, administeredByRoute, intramuscular injection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administeredByRoute Context triple: [Prevnar 13, administeredByRoute, intramuscular injection]
-
A.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
B.
administeredAs
Indicates that one entity is given or applied to another entity as a treatment, dose, or intervention.
-
C.
administeredFor
Indicates that something (typically a treatment, medication, or intervention) is given or applied to an entity for a specific purpose, condition, or intended effect.
-
D.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
E.
administrationRoute
chosen
Indicates the method or pathway by which a substance or treatment is delivered to a subject or system.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.