Triple

T26175597
Position Surface form Disambiguated ID Type / Status
Subject Behçet's disease E654529 entity
Predicate canCauseComplication P18423 FINISHED
Object intestinal perforation 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: intestinal perforation | Statement: [Behçet's disease, canCauseComplication, intestinal perforation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canCauseComplication
Context triple: [Behçet's disease, canCauseComplication, intestinal perforation]
  • A. causesSocialComplicationsFor
    Indicates that one entity’s behavior, condition, or presence leads to difficulties, conflicts, or awkward situations in another entity’s social interactions or relationships.
  • B. complicationType
    Indicates the specific kind or category of complication associated with an event, condition, or process.
  • C. complication chosen
    Indicates that one event, action, or condition makes another more difficult, problematic, or introduces an additional obstacle or entanglement in the situation.
  • D. possibleCauseOf
    Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
  • E. mayBeComorbidWith
    Indicates that two conditions or disorders can occur together in the same individual, potentially influencing each other’s presence or severity.
  • 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_69ee5b45873c81909499203612d05d07 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f612607c388190ab61d1ac7d18e08d completed May 2, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69f611a9272881909093360472be832c completed May 2, 2026, 3 p.m.
Created at: April 26, 2026, 8:37 p.m.