Triple
T34091888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acomplia |
E874318
|
entity |
| Predicate | regulatoryDecisionInUnitedStates |
P9662
|
FINISHED |
| Object | never approved |
—
|
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: never approved | Statement: [Acomplia, regulatoryDecisionInUnitedStates, never approved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryDecisionInUnitedStates Context triple: [Acomplia, regulatoryDecisionInUnitedStates, never approved]
-
A.
regulatoryOutcome
chosen
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.
-
B.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
C.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
D.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
E.
displayRegulation
Indicates that an entity presents or shows a regulation or set of rules, making it visible or accessible to others.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:52 a.m.