Triple

T5425230
Position Surface form Disambiguated ID Type / Status
Subject relapsing-remitting multiple sclerosis E121346 entity
Predicate relapseSeparationInterval P28046 FINISHED
Object at least 30 days between attacks 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: at least 30 days between attacks | Statement: [relapsing-remitting multiple sclerosis, relapseSeparationInterval, at least 30 days between attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relapseSeparationInterval
Context triple: [relapsing-remitting multiple sclerosis, relapseSeparationInterval, at least 30 days between attacks]
  • A. breakupTimeInterval
    Indicates the time period during which a breakup between entities occurs or is in effect.
  • B. recurrenceIntervalEstimate chosen
    Indicates an estimated length of time between successive occurrences of the same event or condition.
  • C. dosingInterval
    Indicates the time period that should elapse between consecutive doses of a medication or treatment.
  • D. displacementPeriod
    Indicates the time interval over which an entity is moved or shifted from one position or state to another.
  • E. refusalPeriodMaximum
    Indicates the maximum allowed duration within which a refusal can occur or remain valid in the context of the related relationship or action.
  • 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_69bd463b58d88190b258261573de9e91 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8911a7348190ad9378a248190f07 completed March 20, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69bd846b8bdc81909dcdc2a3084226f2 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:06 p.m.