Triple
T8976718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumbernauld |
E214408
|
entity |
| Predicate | townCentreDesign |
P52509
|
FINISHED |
| Object | multi-level megastructure |
—
|
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: multi-level megastructure | Statement: [Cumbernauld, townCentreDesign, multi-level megastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townCentreDesign Context triple: [Cumbernauld, townCentreDesign, multi-level megastructure]
-
A.
urbanDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or shaping the physical layout and functional structure of urban spaces.
-
B.
urbanDesigner
Indicates a relationship where an entity practices or is responsible for planning and designing urban spaces, environments, or city layouts.
-
C.
urbanDesignType
chosen
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
-
D.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
E.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6786c880819088393bb107a7364c |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.