Triple

T9807164
Position Surface form Disambiguated ID Type / Status
Subject Xeloda E238181 entity
Predicate isActivatedPreferentiallyIn P90096 FINISHED
Object tumor tissue 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: tumor tissue | Statement: [Xeloda, isActivatedPreferentiallyIn, tumor tissue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isActivatedPreferentiallyIn
Context triple: [Xeloda, isActivatedPreferentiallyIn, tumor tissue]
  • A. isPreferredWhen
    Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
  • B. activatedFor
    Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
  • C. canBeActivatedFor
    Indicates that one entity is capable of being put into an active or operational state by or for another entity.
  • D. isPotentiallyActive
    Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
  • E. isSelective
    Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
  • 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_69ca84defac48190abc1148804f184c1 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdab7cb9588190953a063cb7b9e29e completed April 1, 2026, 11:34 p.m.
PD Predicate disambiguation batch_69cd03dd2da881909052fbf29736a773 completed April 1, 2026, 11:39 a.m.
PDg Predicate description generation batch_69cd06abc9248190a506b64e9c516d03 completed April 1, 2026, 11:51 a.m.
Created at: March 30, 2026, 8:29 p.m.