Triple

T33862186
Position Surface form Disambiguated ID Type / Status
Subject Scottish devolution E867952 entity
Predicate transfersPowerFrom P173782 FINISHED
Object Parliament of the United Kingdom 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: Parliament of the United Kingdom | Statement: [Scottish devolution, transfersPowerFrom, Parliament of the United Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transfersPowerFrom
Context triple: [Scottish devolution, transfersPowerFrom, Parliament of the United Kingdom]
  • A. transferredPowerTo
    Indicates that one entity has passed control, authority, or energy to another entity.
  • B. derivesPowerFrom chosen
    Indicates that one entity obtains or is granted its power, authority, or energy as a result of another entity.
  • C. usesPowerFor
    Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
  • D. inPower
    Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
  • E. reservesPowerTo
    Indicates that one party retains or explicitly keeps for itself the authority or right to exercise a particular power or function, rather than granting it to others.
  • 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_69f349943ccc8190a3c41a3e0ae46cbf completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff109695008190a22b47ef8be2e3f9 completed May 9, 2026, 10:46 a.m.
PD Predicate disambiguation batch_69ff0f243ea88190970d2c520b55c816 completed May 9, 2026, 10:40 a.m.
Created at: May 1, 2026, 1:47 a.m.