Triple

T6004848
Position Surface form Disambiguated ID Type / Status
Subject C9orf72 E133683 entity
Predicate repeatExpansionDetectedBy P68679 FINISHED
Object repeat-primed PCR 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: repeat-primed PCR | Statement: [C9orf72, repeatExpansionDetectedBy, repeat-primed PCR]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: repeatExpansionDetectedBy
Context triple: [C9orf72, repeatExpansionDetectedBy, repeat-primed PCR]
  • A. restrictedExpansionOf
    Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
  • B. repetitionOf
    Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
  • C. causesRepetitionOf
    Indicates that one entity brings about or is responsible for the recurrence or repeated occurrence of another entity or event.
  • D. usesRepetition
    Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
  • E. expansionReason
    Indicates the reason or cause behind an expansion event or process occurring between entities.
  • 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_69c00872444c8190bfaf1739dcec765c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f10d18081908c351170b7f58d3d completed March 22, 2026, 8:20 p.m.
PD Predicate disambiguation batch_69c049e3316c819087ea635fa7ee8472 completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04e8c5bfc8190b986a7071d1b23e3 completed March 22, 2026, 8:18 p.m.
Created at: March 22, 2026, 4:06 p.m.