Triple
T27660099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rinvoq |
E697098
|
entity |
| Predicate | approvalAgency |
P807
|
FINISHED |
| Object | U.S. Food and Drug Administration |
E13297
|
NE 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: U.S. Food and Drug Administration | Statement: [Rinvoq, approvalAgency, U.S. Food and Drug Administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvalAgency Context triple: [Rinvoq, approvalAgency, U.S. Food and Drug Administration]
-
A.
approvalFor
Indicates that one entity grants or has granted permission or consent for another entity’s action, request, or status.
-
B.
publicAgency
Indicates that an entity functions as a government-controlled or government-authorized organization that provides public services or carries out public administration.
-
C.
approvalStatute
Indicates that an entity is approved, authorized, or governed under a specific statute or legal provision.
-
D.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
approvalType
Indicates the specific category or kind of approval that has been granted or requested in the relationship between entities.
- F. None of above.
Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12e4475b288190979f9e67f1605150 |
completed | May 24, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 2:36 p.m.