Triple
T7298299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocaine |
E167778
|
entity |
| Predicate | canBeAdministeredBy |
P76074
|
FINISHED |
| Object | snorting |
—
|
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: snorting | Statement: [Cocaine, canBeAdministeredBy, snorting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdministeredBy Context triple: [Cocaine, canBeAdministeredBy, snorting]
-
A.
coAdministersWith
Indicates that one entity is administered together with another entity, typically at the same time or as part of the same treatment or process.
-
B.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
C.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
D.
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.
-
E.
administeredWith
Indicates that two or more treatments, drugs, or interventions are given to a patient at the same time or as part of the same therapeutic regimen.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8f83c881909e8eae85410f9659 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3 p.m.