Triple
T33388496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pomalidomide |
E854983
|
entity |
| Predicate | hasPregnancyPreventionRequirement |
P203492
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [pomalidomide, hasPregnancyPreventionRequirement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPregnancyPreventionRequirement Context triple: [pomalidomide, hasPregnancyPreventionRequirement, yes]
-
A.
requiresCelibacyFor
Indicates that one entity imposes a requirement of celibacy on another entity as a condition for participation, membership, role, or status.
-
B.
hasPregnancyCategory
Indicates the classification of a drug or substance based on its known or potential risks when used during pregnancy.
-
C.
hasProphylaxis
Indicates that an entity is provided with, or subject to, a preventive measure or treatment intended to avert a particular condition or outcome.
-
D.
hasGenderRequirement
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
E.
hasStageOfPregnancy
Indicates that an entity is in, or associated with, a specific stage or phase of pregnancy.
- F. None of above. chosen
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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
| PDg | Predicate description generation | batch_6a0190370290819096183e9fb7d32cff |
completed | May 11, 2026, 8:15 a.m. |
Created at: May 1, 2026, 1:35 a.m.