Triple

T24951130
Position Surface form Disambiguated ID Type / Status
Subject Bardney Group Parish Council E624338 entity
Predicate amenityScope P157271 FINISHED
Object parish-level amenities 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: parish-level amenities | Statement: [Bardney Group Parish Council, amenityScope, parish-level amenities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: amenityScope
Context triple: [Bardney Group Parish Council, amenityScope, parish-level amenities]
  • A. amenity
    Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
  • B. amenityContext
    Indicates the situational or environmental setting in which an amenity is provided, used, or relevant.
  • C. amenityFocus
    Indicates a relationship where an amenity is specifically oriented toward, designed for, or primarily serving a particular focus or target (such as a user group, activity, or purpose).
  • D. amenityLevel
    Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
  • E. hasCivicAmenity
    Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
  • 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_69e2ff22e4c48190a0444b5a044f14e8 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f424004d588190abe0115931aab67a completed May 1, 2026, 3:54 a.m.
PD Predicate disambiguation batch_69f4210130d08190ae30b7943f7a0bbc completed May 1, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f423637bec8190a1701421ac86a3b7 completed May 1, 2026, 3:52 a.m.
Created at: April 18, 2026, 5:56 a.m.