Triple
T34091542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vigabatrin |
E874312
|
entity |
| Predicate | hasRiskManagementProgram |
P80826
|
FINISHED |
| Object | REMS program in the United States |
—
|
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: REMS program in the United States | Statement: [vigabatrin, hasRiskManagementProgram, REMS program in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskManagementProgram Context triple: [vigabatrin, hasRiskManagementProgram, REMS program in the United States]
-
A.
riskManagementProgramName
Indicates the specific name assigned to a risk management program associated with an entity or activity.
-
B.
hasHazardManagement
Indicates that an entity has measures, systems, or responsibilities in place to control, mitigate, or respond to identified hazards.
-
C.
riskManagementMechanism
chosen
Indicates a mechanism, process, or control used to identify, assess, mitigate, or monitor risks associated with an entity or activity.
-
D.
riskManagement
Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
-
E.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 1:52 a.m.