Triple
T24596623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rastrick |
E608689
|
entity |
| Predicate | localWardOf |
P14475
|
FINISHED |
| Object | Calderdale Council |
—
|
NE NERFINISHED |
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: Calderdale Council | Statement: [Rastrick, localWardOf, Calderdale Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localWardOf Context triple: [Rastrick, localWardOf, Calderdale Council]
-
A.
electoralWardFor
Indicates that one entity serves as the electoral ward or voting district in which another entity (such as a place or address) is located or represented.
-
B.
containsWard
chosen
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
C.
locatedInCityWard
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
D.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
E.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:30 a.m.