Triple

T9406581
Position Surface form Disambiguated ID Type / Status
Subject State Administration Council E226601 entity
Predicate delayed P89001 FINISHED
Object promised elections multiple times 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: promised elections multiple times | Statement: [State Administration Council, delayed, promised elections multiple times]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: delayed
Context triple: [State Administration Council, delayed, promised elections multiple times]
  • A. delayedBy
    Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
  • B. mayDelay
    Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
  • C. delayedUntil
    Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
  • D. halted
    Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
  • E. laterIn
    Indicates that one event, state, or time point occurs after another in temporal order.
  • 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_69ca843280488190bc65600e843ef9e6 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd51c3fc988190ac34cc9e09f8ebfc completed April 1, 2026, 5:11 p.m.
PD Predicate disambiguation batch_69cca54c37f88190bddccf28e5fe5c84 completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca9d07eb08190866eb15333386dfa completed April 1, 2026, 5:14 a.m.
Created at: March 30, 2026, 7:47 p.m.