Triple

T33292282
Position Surface form Disambiguated ID Type / Status
Subject Portola Pharmaceuticals E852346 entity
Predicate pipelineFocus P176459 FINISHED
Object hematologic disorders 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: hematologic disorders | Statement: [Portola Pharmaceuticals, pipelineFocus, hematologic disorders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pipelineFocus
Context triple: [Portola Pharmaceuticals, pipelineFocus, hematologic disorders]
  • A. pipelineTo
    Indicates that data, output, or results from one process, component, or stage are directed and fed as input into another in a sequential flow.
  • B. pipeline
    Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
  • C. pipelineDestination
    Indicates that one entity serves as the target or endpoint to which a pipeline directs its output or flow.
  • D. pipelineConfiguration
    Indicates that one entity defines or specifies the configuration settings or structure used by a processing pipeline associated with another entity.
  • E. pipelineOperator
    Indicates that one entity functions as an operator responsible for managing, controlling, or maintaining a pipeline associated with another entity.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
PDg Predicate description generation batch_69f6e312d7fc819094dec41810f2585d completed May 3, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:32 a.m.