Triple
T21895069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berwick-upon-Tweed (UK Parliament constituency) |
E540656
|
entity |
| Predicate | hasRuralElectorate |
P105482
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Berwick-upon-Tweed (UK Parliament constituency), hasRuralElectorate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuralElectorate Context triple: [Berwick-upon-Tweed (UK Parliament constituency), hasRuralElectorate, true]
-
A.
isRuralConstituency
chosen
Indicates that a given constituency is classified as rural rather than urban or suburban.
-
B.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
-
C.
isRemoteElectorate
Indicates that an electorate is classified as geographically remote or distant from major population centers.
-
D.
hasRuralCouncilStatus
Indicates that an entity holds the official designation or legal status of a rural council within a given administrative or governance system.
-
E.
hasRuralSection
Indicates that an entity includes, contains, or is associated with a portion or segment located in a rural 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc6062c81908bf0aad7c6b99932 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.