Triple

T36600563
Position Surface form Disambiguated ID Type / Status
Subject APHINITY E902901 entity
Predicate safetyFinding P32502 FINISHED
Object cardiac safety profile was acceptable and similar between arms 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: cardiac safety profile was acceptable and similar between arms | Statement: [APHINITY, safetyFinding, cardiac safety profile was acceptable and similar between arms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safetyFinding
Context triple: [APHINITY, safetyFinding, cardiac safety profile was acceptable and similar between arms]
  • A. safety
    Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
  • B. safetyRelevant
    Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
  • C. safetyIssueHighlighted
    Indicates that a particular safety concern or hazard has been identified and explicitly brought to attention.
  • D. observationSafety
    Indicates that an observation or monitoring activity is conducted in a manner that ensures the safety of the subjects, observers, and environment involved.
  • E. notableSafety chosen
    Indicates that an entity is recognized for having significant safety characteristics, performance, or impact relative to others.
  • 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_69f76e66b7b88190848f7a3e1188915f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f9fd6834cc8190aa27153d6a99f3bb completed May 5, 2026, 2:23 p.m.
PD Predicate disambiguation batch_69f7cf769338819092a5f42653dcc956 completed May 3, 2026, 10:43 p.m.
Created at: May 3, 2026, 4:11 p.m.