Triple

T277874
Position Surface form Disambiguated ID Type / Status
Subject Official Opposition (United Kingdom) E5287 entity
Predicate mayChangeAfter P4054 FINISHED
Object general election 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 | Statement: [Official Opposition (United Kingdom), mayChangeAfter, general election]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayChangeAfter
Context triple: [Official Opposition (United Kingdom), mayChangeAfter, general election]
  • A. mayExtendTo
    Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
  • B. changeReason
    Indicates the reason or justification for a modification or change made to an entity or its state.
  • C. hasLegalChange
    Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
  • D. canSet
    Indicates that one entity has the ability or permission to assign, configure, or change a property, value, or state of another entity.
  • E. reassessedAfter chosen
    Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25dee7830819087f153769a8496b9 completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b7480e881909399beccfc7ffb81 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.