Triple
T27925232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stowey-Sutton |
E707813
|
entity |
| Predicate | parishCouncilResponsibleFor |
P163781
|
FINISHED |
| Object | local planning applications |
—
|
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: local planning applications | Statement: [Stowey-Sutton, parishCouncilResponsibleFor, local planning applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishCouncilResponsibleFor Context triple: [Stowey-Sutton, parishCouncilResponsibleFor, local planning applications]
-
A.
civilParishCouncil
Indicates that a civil parish is governed or administered by a particular parish council.
-
B.
hasParishCouncils
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
C.
overseesParish
Indicates that one entity has administrative or supervisory responsibility over a parish.
-
D.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
E.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:59 p.m.