Triple
T2709105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leigh (UK Parliament constituency) |
E59813
|
entity |
| Predicate | boundaryChange |
P21193
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Leigh (UK Parliament constituency), boundaryChange, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryChange Context triple: [Leigh (UK Parliament constituency), boundaryChange, 1918]
-
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.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
D.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
E.
alignmentChange
Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7542548190bbf6c947145f7f63 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.