Triple
T23855261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster parliamentary constituency |
E592287
|
entity |
| Predicate | hasBoundaryReview |
P75350
|
FINISHED |
| Object | periodic boundary review |
—
|
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: periodic boundary review | Statement: [Westminster parliamentary constituency, hasBoundaryReview, periodic boundary review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryReview Context triple: [Westminster parliamentary constituency, hasBoundaryReview, periodic boundary review]
-
A.
hasBoundaryReviewBody
Indicates that an entity has an associated body or authority responsible for reviewing or overseeing its boundaries.
-
B.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
C.
boundaryReviewRegion
Indicates that a specified region is under consideration or subject to evaluation in a boundary review process.
-
D.
boundaryReviewEvent
chosen
Indicates an event in which the boundaries or limits of something are formally examined, evaluated, or adjusted.
-
E.
abolishedInBoundaryReview
Indicates that an electoral or administrative unit was eliminated as a result of a formal boundary review process.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:12 p.m.