Triple
T32354642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Borough of Bradford |
E826699
|
entity |
| Predicate | cityStatusAppliesTo |
P174178
|
FINISHED |
| Object | Bradford |
—
|
NE NERFINISHED |
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: Bradford | Statement: [Metropolitan Borough of Bradford, cityStatusAppliesTo, Bradford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStatusAppliesTo Context triple: [Metropolitan Borough of Bradford, cityStatusAppliesTo, Bradford]
-
A.
cityStatusContext
Indicates the contextual status or role that a city holds within a broader administrative, political, or situational framework.
-
B.
impliesStatusOfCity
Indicates that one entity suggests, infers, or entails a particular status or condition of a city.
-
C.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
D.
cityDistrictStatus
Indicates the administrative or legal status that a city district holds within its governing jurisdiction.
-
E.
cityStatusGrantedBy
Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be5f3b048190ae36a644b56d2f95 |
completed | May 3, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:49 a.m.