Triple

T24366222
Position Surface form Disambiguated ID Type / Status
Subject Glasgow City Region E614200 entity
Predicate hasDevolutionType P155937 FINISHED
Object city deal 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: city deal | Statement: [Glasgow City Region, hasDevolutionType, city deal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDevolutionType
Context triple: [Glasgow City Region, hasDevolutionType, city deal]
  • A. hasDevolutionContext
    Indicates that something is associated with, or occurs within, a specific context of devolution (such as the transfer or delegation of powers or responsibilities).
  • B. typeOfDevolutionChange
    Indicates a change in the form, level, or structure of devolved authority or responsibilities from one entity to another.
  • C. hasDevolvedMatters
    Indicates that certain powers or responsibilities have been transferred from a central authority to a subordinate or regional authority.
  • D. hasDevolvedBody
    Indicates that authority, responsibility, or powers have been transferred from a central entity to a subordinate or regional entity.
  • E. hasDevelopmentType
    Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
  • 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_69e2d7dfe7f08190b7a1f3a36483ab05 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2938809f081908abf33edb62ed7f8 completed April 29, 2026, 11:26 p.m.
PD Predicate disambiguation batch_69f287bb1b2c81909c2e7fcc392ad143 completed April 29, 2026, 10:35 p.m.
PDg Predicate description generation batch_69f28f4d978c81908310c01def2514cc completed April 29, 2026, 11:07 p.m.
Created at: April 18, 2026, 2:01 a.m.