Triple
T24894130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury St Edmunds (UK Parliament constituency) |
E623087
|
entity |
| Predicate | previousExistenceAsBorough |
P158744
|
FINISHED |
| Object | before 1885 |
—
|
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: before 1885 | Statement: [Bury St Edmunds (UK Parliament constituency), previousExistenceAsBorough, before 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousExistenceAsBorough Context triple: [Bury St Edmunds (UK Parliament constituency), previousExistenceAsBorough, before 1885]
-
A.
previousBorough
Indicates that one borough directly precedes another in a defined ordering or sequence.
-
B.
hasBoroughEquivalent
Indicates that one administrative area corresponds functionally or hierarchically to a borough in another jurisdiction or classification system.
-
C.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
E.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
- F. None of above. chosen
Provenance (4 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 5:26 a.m.