Triple
T5267073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgnorth |
E118962
|
entity |
| Predicate | formerDistrictStatus |
P20255
|
FINISHED |
| Object | municipal borough |
—
|
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: municipal borough | Statement: [Bridgnorth, formerDistrictStatus, municipal borough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDistrictStatus Context triple: [Bridgnorth, formerDistrictStatus, municipal borough]
-
A.
formerDistrict
chosen
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
B.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
C.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
D.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
E.
redistrictedFrom
Indicates that one political or administrative district has been created, altered, or derived from another through a redistricting 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.