Triple
T22693616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teglutik |
E561110
|
entity |
| Predicate | hasAdministrationDevice |
P54326
|
FINISHED |
| Object | oral dosing syringe |
—
|
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: oral dosing syringe | Statement: [Teglutik, hasAdministrationDevice, oral dosing syringe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrationDevice Context triple: [Teglutik, hasAdministrationDevice, oral dosing syringe]
-
A.
administeredWithDevice
chosen
Indicates that an action or treatment is carried out using a specific device as the means or instrument of administration.
-
B.
hasAdministrationMethod
Indicates the method or route by which something (typically a drug, treatment, or resource) is administered or delivered.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
hasAlterEgoDevice
Indicates that an entity possesses or is associated with a device specifically used to enable, support, or manifest its alter ego.
-
E.
supportsDeviceManagement
Indicates that one entity provides capabilities or functionality to manage, configure, or control another entity’s devices.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.