Triple

T33442216
Position Surface form Disambiguated ID Type / Status
Subject Carrickfergus Borough Council E856393 entity
Predicate governedOnLevel P77956 FINISHED
Object district 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: district | Statement: [Carrickfergus Borough Council, governedOnLevel, district]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governedOnLevel
Context triple: [Carrickfergus Borough Council, governedOnLevel, district]
  • A. governedForLevel
    Indicates that an entity exercises governing authority or control specifically applicable to a particular level (such as a tier, layer, or hierarchy stage).
  • B. governedFor
    Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
  • C. governedWith
    Indicates that two or more entities share or participate together in the act or process of governing.
  • D. hasGovernanceLevel chosen
    Indicates the degree or tier of authority, control, or decision-making power that an entity holds within a governance structure.
  • E. governedThrough
    Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
  • 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_69f34971b75881908be360bb041f003c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a00a2f0d1588190a936ea7df0ef0464 completed May 10, 2026, 3:23 p.m.
PD Predicate disambiguation batch_6a00a28ccd94819085b5e123f5a4769e completed May 10, 2026, 3:21 p.m.
Created at: May 1, 2026, 1:37 a.m.