Triple
T8790851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Towns Act 1965 |
E209159
|
entity |
| Predicate | typeOfUrbanPolicy |
P85409
|
FINISHED |
| Object | growth centre policy |
—
|
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: growth centre policy | Statement: [New Towns Act 1965, typeOfUrbanPolicy, growth centre policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfUrbanPolicy Context triple: [New Towns Act 1965, typeOfUrbanPolicy, growth centre policy]
-
A.
mainUrbanPlan
Indicates the primary urban planning scheme or framework that governs the development and organization of a given area.
-
B.
cityPolicy
Indicates a relationship where a city establishes or is governed by a specific policy, rule, or regulatory framework.
-
C.
urbanDevelopmentType
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
D.
hasUrbanPlanning
Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
-
E.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8d25f881908863d636fa57a8a2 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:43 p.m.