Triple
T24108409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivitrol |
E597292
|
entity |
| Predicate | routeDetail |
P155091
|
FINISHED |
| Object | deep intramuscular injection in the gluteal 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: deep intramuscular injection in the gluteal muscle | Statement: [Vivitrol, routeDetail, deep intramuscular injection in the gluteal muscle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeDetail Context triple: [Vivitrol, routeDetail, deep intramuscular injection in the gluteal muscle]
-
A.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
B.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
E.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de19057c819096a8b3290d33e2f6 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:02 p.m.