Triple

T34091900
Position Surface form Disambiguated ID Type / Status
Subject Acomplia E874318 entity
Predicate effectOnLipidProfile P138247 FINISHED
Object improves HDL cholesterol 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: improves HDL cholesterol | Statement: [Acomplia, effectOnLipidProfile, improves HDL cholesterol]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: effectOnLipidProfile
Context triple: [Acomplia, effectOnLipidProfile, improves HDL cholesterol]
  • A. associatedWithLipidMetabolism chosen
    Indicates a relationship where a process, molecule, or entity is involved in, influences, or is functionally connected to lipid metabolism.
  • B. associatedWithTriglycerides
    Indicates a relationship in which something has a connection or relevance to triglycerides, such as influencing, being influenced by, or otherwise linked to them.
  • C. isLipid
    Indicates that the subject entity is classified as a lipid or belongs to the category of lipid molecules.
  • D. modifiesPharmacokineticsOf
    Indicates that one entity alters the absorption, distribution, metabolism, or excretion characteristics of another entity.
  • E. healthEffect
    Indicates the impact or consequence that one entity has on the health or well-being of 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_69f349a735208190a1dbfb1c2a121059 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fd231cab588190ad0953dc8f4af8f2 completed May 7, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69fd1aa3f1c481909fe6e9cab1383551 completed May 7, 2026, 11:05 p.m.
Created at: May 1, 2026, 1:52 a.m.