Triple
T33291976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitoxantrone |
E852340
|
entity |
| Predicate | hasApprovalFor |
P137282
|
FINISHED |
| Object | multiple sclerosis (US, restricted use) |
—
|
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: multiple sclerosis (US, restricted use) | Statement: [Mitoxantrone, hasApprovalFor, multiple sclerosis (US, restricted use)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApprovalFor Context triple: [Mitoxantrone, hasApprovalFor, multiple sclerosis (US, restricted use)]
-
A.
hasApprovalType
Indicates that an entity is associated with a specific category or kind of approval it has received or requires.
-
B.
isApprovedFor
chosen
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
-
C.
hasApprovalAuthority
Indicates that an entity possesses the power or right to review and formally approve or reject decisions, actions, or requests made by others.
-
D.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
approvedAt
Indicates the date and time at which an entity received formal approval.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 1:32 a.m.