Triple
T9300567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Lancashire |
E223747
|
entity |
| Predicate | districtStatus |
P37705
|
FINISHED |
| Object | non-metropolitan district |
—
|
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: non-metropolitan district | Statement: [West Lancashire, districtStatus, non-metropolitan district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtStatus Context triple: [West Lancashire, districtStatus, non-metropolitan district]
-
A.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
B.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
C.
districtAdministration
Indicates that an entity is responsible for managing, governing, or overseeing the administrative affairs of a specific district or local jurisdiction.
-
D.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d1d954819098be177addafa406 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.