Triple

T35313526
Position Surface form Disambiguated ID Type / Status
Subject ULTRA E1019840 entity
Predicate wasDeclassifiedBy P63993 FINISHED
Object United Kingdom government NE NERFINISHED

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: United Kingdom government | Statement: [ULTRA, wasDeclassifiedBy, United Kingdom government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasDeclassifiedBy
Context triple: [ULTRA, wasDeclassifiedBy, United Kingdom government]
  • A. declassified
    Indicates that information or material has been officially downgraded from a restricted or secret status, making it accessible to a wider audience or the public.
  • B. canBeDeclassifiedBy chosen
    Indicates that an item currently classified or restricted may be lawfully downgraded or released by a specified authority or entity.
  • C. wasFormerlyClassifiedAs
    Indicates that an entity previously belonged to a particular class or category but no longer does so.
  • D. mayBeDeclassified
    Indicates that an item currently classified or restricted is eligible or permitted to have its classification status removed or lowered.
  • E. partlyDeclassified
    Indicates that the information or document has had only some portions declassified, while other parts remain classified.
  • 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_69f76de9d45c81908a2ed0956b448b65 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7908ec35881909a42f954fb9fa16e completed May 3, 2026, 6:14 p.m.
PD Predicate disambiguation batch_69f78e2f52e08190a77661223a96c601 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:03 p.m.