Triple
T9524790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | levodopa |
E229731
|
entity |
| Predicate | approvedForMedicalUse |
P24602
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [levodopa, approvedForMedicalUse, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedForMedicalUse Context triple: [levodopa, approvedForMedicalUse, 1960s]
-
A.
medicinalUse
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
B.
approvedDrugForm
Indicates that a particular pharmaceutical form (e.g., tablet, injection) is an officially approved formulation of a given drug.
-
C.
potentialTherapeuticUse
Indicates that something is being considered or investigated as a possible treatment or therapy for a condition or disease.
-
D.
FDAApprovalType
Indicates the specific regulatory pathway or category under which a product has been approved by the U.S. Food and Drug Administration.
-
E.
hasRegulatoryApproval
chosen
Indicates that an entity has received formal authorization or clearance from a relevant regulatory authority to operate, be sold, or be used in a specified context.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9899f99481908d374528716027f8 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.