Triple
T29353020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cipla |
E744362
|
entity |
| Predicate | regulatoryApprovalFrom |
P149280
|
FINISHED |
| Object | US Food and Drug Administration |
—
|
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: US Food and Drug Administration | Statement: [Cipla, regulatoryApprovalFrom, US Food and Drug Administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryApprovalFrom Context triple: [Cipla, regulatoryApprovalFrom, US Food and Drug Administration]
-
A.
hasRegulatoryApproval
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.
receivedUSFDAApprovalFor
chosen
Indicates that an entity has obtained official approval from the U.S. Food and Drug Administration (FDA) for a specific product, use, or application.
-
C.
FDAApprovalType
Indicates the specific regulatory pathway or category under which a product has been approved by the U.S. Food and Drug Administration.
-
D.
regulatoryApprovalYear
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
E.
isApprovedFor
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 2:08 p.m.