Triple
T28510969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolton postcode area |
E721481
|
entity |
| Predicate | servesNonMetropolitanDistrict |
P121591
|
FINISHED |
| Object | Rossendale |
—
|
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: Rossendale | Statement: [Bolton postcode area, servesNonMetropolitanDistrict, Rossendale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesNonMetropolitanDistrict Context triple: [Bolton postcode area, servesNonMetropolitanDistrict, Rossendale]
-
A.
servesSuburbsOf
Indicates that a service, route, or facility provides coverage or support to the suburban areas associated with a particular city or region.
-
B.
servesGovernmentDistrict
chosen
Indicates that an entity provides official services or representation to a specific government district.
-
C.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
-
D.
servedDistrict
Indicates that an entity has provided official service or representation to a particular district.
-
E.
servesRuralArea
Indicates that an entity provides services or support specifically to people or communities located in rural areas.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 3:12 a.m.