Triple
T16952367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enovid |
E411214
|
entity |
| Predicate | progestinComponent |
P30732
|
FINISHED |
| Object | norethynodrel |
—
|
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: norethynodrel | Statement: [Enovid, progestinComponent, norethynodrel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progestinComponent Context triple: [Enovid, progestinComponent, norethynodrel]
-
A.
isProdrugOf
Indicates that one substance is a precursor form that is metabolized in the body to produce the active form of another substance.
-
B.
reproductiveCare
Indicates the provision or receipt of services, support, or actions related to an entity’s reproductive health and reproductive processes.
-
C.
coFormulated
Indicates that two or more entities were jointly formulated, designed, or created together as part of the same process or product.
-
D.
isNonSteroidal
Indicates that something does not possess steroidal characteristics or is not derived from steroids.
-
E.
coFormulatedWith
chosen
Indicates that one entity is formulated together with another as part of the same combined product or composition.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.