Triple

T14771592
Position Surface form Disambiguated ID Type / Status
Subject Rugby (UK Parliament constituency) E347146 entity
Predicate representationInterrupted P105676 FINISHED
Object 1983–2010 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: 1983–2010 | Statement: [Rugby (UK Parliament constituency), representationInterrupted, 1983–2010]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: representationInterrupted
Context triple: [Rugby (UK Parliament constituency), representationInterrupted, 1983–2010]
  • A. wasInterruptedBy
    Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
  • B. statusAtInterruption
    Indicates the specific state or condition something was in at the moment it was interrupted.
  • C. disruptedIn chosen
    Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
  • D. reignInterrupted
    Indicates that a ruler’s period of governance was broken by one or more interruptions rather than being continuous.
  • E. constructionInterruptedBy
    Indicates that an ongoing construction process is halted, delayed, or disrupted due to the actions or occurrence of another specified entity or event.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec81334e08190a77d760e507d00ed completed April 14, 2026, 11:04 p.m.
PD Predicate disambiguation batch_69de8c02e5c08190943c27594026faf7 completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:31 a.m.