Triple

T32808926
Position Surface form Disambiguated ID Type / Status
Subject UK parliamentary by-elections E839091 entity
Predicate notHeldWhen P8096 FINISHED
Object general election is imminent 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: general election is imminent | Statement: [UK parliamentary by-elections, notHeldWhen, general election is imminent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notHeldWhen
Context triple: [UK parliamentary by-elections, notHeldWhen, general election is imminent]
  • A. notHeldDuring chosen
    Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
  • B. notHeldIn
    Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
  • C. notAutomaticallyHeldBy
    Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
  • D. notHeldReason
    Indicates the reason or cause why a particular event, action, or state did not occur or was not carried out.
  • E. didNotHold
    Indicates that an expected event, condition, or relationship failed to occur or be valid.
  • 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_69f3493d35208190b4351b4e85f2fa16 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6ce6d659881909ddcec1d2966e020 completed May 3, 2026, 4:26 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 1:15 a.m.