Triple
T24850893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RNA therapeutics |
E621880
|
entity |
| Predicate | regulatoryApprovedExample |
P24602
|
FINISHED |
| Object | givosiran |
—
|
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: givosiran | Statement: [RNA therapeutics, regulatoryApprovedExample, givosiran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryApprovedExample Context triple: [RNA therapeutics, regulatoryApprovedExample, givosiran]
-
A.
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.
-
B.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
-
C.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
D.
regulatoryOutcome
Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
-
E.
appliesRegulatoryStandard
Indicates that one entity enforces or uses a specific regulatory standard in relation to another entity or 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 5:20 a.m.