Triple

T7222018
Position Surface form Disambiguated ID Type / Status
Subject Wales Act 1978 E150281 entity
Predicate reasonForNonCommencement P75534 FINISHED
Object failure of 1979 Welsh devolution referendum 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: failure of 1979 Welsh devolution referendum | Statement: [Wales Act 1978, reasonForNonCommencement, failure of 1979 Welsh devolution referendum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForNonCommencement
Context triple: [Wales Act 1978, reasonForNonCommencement, failure of 1979 Welsh devolution referendum]
  • A. reasonForNotCompletion
    Indicates the explanation or cause for why a task, process, or obligation was not completed.
  • B. postponementReason
    Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
  • C. reasonForNonParticipation
    Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
  • D. reasonForNonOperation
    Indicates the specific cause or explanation for why an entity, system, or process is not currently operating or functioning.
  • E. reasonForNoProduction
    Indicates the specific cause or explanation for why production did not occur.
  • 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_69c687effb44819092b95d07d0368c9f completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e9b42c5c81908c405f161c35ffb4 completed March 27, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69c6e75f84e481909e7866186ae80cff completed March 27, 2026, 8:23 p.m.
PDg Predicate description generation batch_69c6e889854481908c765ce2107f2d3a completed March 27, 2026, 8:28 p.m.
Created at: March 27, 2026, 2:54 p.m.