Triple

T26763446
Position Surface form Disambiguated ID Type / Status
Subject Reedley Hallows civil parish E674869 entity
Predicate hasParishLevel P180395 FINISHED
Object lowest tier of local government in England 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: lowest tier of local government in England | Statement: [Reedley Hallows civil parish, hasParishLevel, lowest tier of local government in England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasParishLevel
Context triple: [Reedley Hallows civil parish, hasParishLevel, lowest tier of local government in England]
  • A. isParishEquivalent
    Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
  • B. hasParishCommunity
    Indicates that an entity is associated with, served by, or belongs to a specific parish community.
  • C. hasParishJurisdiction
    Indicates that one entity holds official parish-level authority or administrative control over another entity or area.
  • D. hasParishFunction
    Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
  • E. haveOwnParishes
    Indicates that an entity possesses or is responsible for its own distinct parishes.
  • 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_69eecda85298819097ee1c38a3d772e7 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
PDg Predicate description generation batch_69f74061c440819080434155c2d60341 completed May 3, 2026, 12:32 p.m.
Created at: April 27, 2026, 3:58 a.m.