Triple
T25091106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmondshire District Council |
E628456
|
entity |
| Predicate | servedCommunitiesIncluding |
P167038
|
FINISHED |
| Object | Richmond |
—
|
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: Richmond | Statement: [Richmondshire District Council, servedCommunitiesIncluding, Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCommunitiesIncluding Context triple: [Richmondshire District Council, servedCommunitiesIncluding, Richmond]
-
A.
servedCommunitiesIn
Indicates that an entity has provided services or support to communities located within a specified area or jurisdiction.
-
B.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
C.
includesCommunitiesFrom
Indicates that one entity encompasses or contains communities that originate from or belong to another entity.
-
D.
includesInSomeCommunities
Indicates that an entity is considered a member or part of certain, but not necessarily all, communities.
-
E.
servesNearbyCommunities
Indicates that an entity provides services or support to communities located in its surrounding 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 18, 2026, 6:24 a.m.