Triple

T5931316
Position Surface form Disambiguated ID Type / Status
Subject Sporothrix E131943 entity
Predicate clinicalForm P66791 FINISHED
Object lymphocutaneous sporotrichosis 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: lymphocutaneous sporotrichosis | Statement: [Sporothrix, clinicalForm, lymphocutaneous sporotrichosis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: clinicalForm
Context triple: [Sporothrix, clinicalForm, lymphocutaneous sporotrichosis]
  • A. clinicalSignOf
    Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
  • B. electronicHealthRecordSystem
    Indicates a relationship where an entity functions as or is associated with an electronic system used to create, store, manage, or access patients’ health records.
  • C. clinicalRole
    Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
  • D. implementationForm
    Indicates the specific manner, format, or method by which something is implemented or realized in practice.
  • E. practiceElement
    Indicates that one entity is a component, step, or sub-activity within a broader practice or procedure involving 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_69c0085b75e88190a632f9691f9da48b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03c9239e08190bff7ef2bd6d21ae0 completed March 22, 2026, 7:01 p.m.
PD Predicate disambiguation batch_69c033541d108190a34d1fde2fe9dacb completed March 22, 2026, 6:22 p.m.
PDg Predicate description generation batch_69c03c8d579081909d7b97fc9014b5d7 completed March 22, 2026, 7:01 p.m.
Created at: March 22, 2026, 4 p.m.