Triple

T19157454
Position Surface form Disambiguated ID Type / Status
Subject Propecia E468960 entity
Predicate shouldNotBeHandledBy P97022 FINISHED
Object pregnant women 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: pregnant women | Statement: [Propecia, shouldNotBeHandledBy, pregnant women]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shouldNotBeHandledBy
Context triple: [Propecia, shouldNotBeHandledBy, pregnant women]
  • A. doesNotUsuallyHandle
    Indicates that an entity is generally not responsible for or typically involved in performing a particular task, role, or type of item, even if it might do so in rare or exceptional cases.
  • B. shouldNotBeUsedWith
    Indicates that one entity is not recommended or is prohibited from being used in combination with another entity.
  • C. doNotApplyTo
    Indicates that something is excluded from affecting, covering, or being relevant to a specified target or case.
  • D. shouldNotBeUsedIn chosen
    Indicates that one entity is not appropriate, allowed, or recommended for use within the context, scope, or situation defined by another entity.
  • E. notTransmittedBy
    Indicates that a particular entity does not serve as a carrier or medium through which something (such as a disease, signal, or information) is passed from one entity to another.
  • 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_69d8dd084ff48190ac0f8c46ee722629 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5eeba91a081909c04d61d6117da06 completed April 20, 2026, 9:15 a.m.
PD Predicate disambiguation batch_69e4b9b83d6881908e6271c620f74100 completed April 19, 2026, 11:17 a.m.
Created at: April 10, 2026, 12:06 p.m.