Triple
T4300168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beswick |
E99814
|
entity |
| Predicate | urbanRegenerationStatus |
P55332
|
FINISHED |
| Object | ongoing |
—
|
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: ongoing | Statement: [Beswick, urbanRegenerationStatus, ongoing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRegenerationStatus Context triple: [Beswick, urbanRegenerationStatus, ongoing]
-
A.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
-
B.
cityStatusContext
Indicates the contextual status or role that a city holds within a broader administrative, political, or situational framework.
-
C.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
D.
urbanDevelopment
Indicates the process or activities through which urban areas are planned, expanded, or transformed, including changes to infrastructure, land use, and the built environment.
-
E.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509e8cb481909ccca7992aac31a3 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:08 p.m.