Triple
T26763308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldshaw Booth |
E674865
|
entity |
| Predicate | parishCouncilWebsite |
P30293
|
FINISHED |
| Object | https://www.goldshawbooth.org.uk |
—
|
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: https://www.goldshawbooth.org.uk | Statement: [Goldshaw Booth, parishCouncilWebsite, https://www.goldshawbooth.org.uk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishCouncilWebsite Context triple: [Goldshaw Booth, parishCouncilWebsite, https://www.goldshawbooth.org.uk]
-
A.
civilParishCouncil
Indicates that a civil parish is governed or administered by a particular parish council.
-
B.
hasLocalGovernmentWebsite
chosen
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
C.
hasParishCouncils
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
D.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
E.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:58 a.m.