Triple
T18101907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashfield (UK Parliament constituency) |
E433239
|
entity |
| Predicate | boundaryChangesOccurredIn |
P21193
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Ashfield (UK Parliament constituency), boundaryChangesOccurredIn, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryChangesOccurredIn Context triple: [Ashfield (UK Parliament constituency), boundaryChangesOccurredIn, 1974]
-
A.
borderChange
chosen
Indicates a change in the boundaries between geographic or political entities, such as when borders are redrawn, expanded, reduced, or otherwise altered over time.
-
B.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
D.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
-
E.
boundaryReviewRegion
Indicates that a specified region is under consideration or subject to evaluation in a 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb6fed8819090798683353a5c08 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.