Triple
T13079693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSD |
E310169
|
entity |
| Predicate | typicalRouteOfAdministration |
P56591
|
FINISHED |
| Object | oral |
—
|
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 | Statement: [LSD, typicalRouteOfAdministration, oral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRouteOfAdministration Context triple: [LSD, typicalRouteOfAdministration, oral]
-
A.
commonRouteOfAdministration
Indicates that two or more substances share the same typical method or pathway by which they are administered to a subject.
-
B.
hasRouteOfAdministration
Indicates that one entity specifies the method or pathway by which another entity (typically a substance or medication) is administered.
-
C.
mainDrugRoute
chosen
Indicates the primary method or pathway by which a drug is administered or delivered to its target.
-
D.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
E.
laterAdministeredAs
Indicates that something was given or applied at a subsequent time, following an earlier event or condition.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98119cb7081908b78ffe83ec99851 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.