Triple
T24108478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aristada |
E597293
|
entity |
| Predicate | loadingRegimenBrand |
P24560
|
FINISHED |
| Object | Aristada Initio |
—
|
NE NERFINISHED |
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: Aristada Initio | Statement: [Aristada, loadingRegimenBrand, Aristada Initio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadingRegimenBrand Context triple: [Aristada, loadingRegimenBrand, Aristada Initio]
-
A.
sponsorDrugBrand
Indicates that one entity financially supports, endorses, or promotes a specific drug brand, typically in a commercial or regulatory context.
-
B.
doseRegimen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
C.
hasLoadingDoseRegimen
chosen
Indicates that an entity is associated with a specific initial (loading) dosing regimen administered to rapidly achieve a desired therapeutic level.
-
D.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
E.
regimenDependsOn
Indicates that the applicability or outcome of a regimen is contingent upon another specified factor, condition, or regimen.
- 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_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. |
Created at: April 17, 2026, 11:02 p.m.