Triple
T9206807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham Canal |
E221000
|
entity |
| Predicate | urbanSectionUse |
P52398
|
FINISHED |
| Object | waterside regeneration |
—
|
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: waterside regeneration | Statement: [Nottingham Canal, urbanSectionUse, waterside regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanSectionUse Context triple: [Nottingham Canal, urbanSectionUse, waterside regeneration]
-
A.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
B.
landUseContext
chosen
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
C.
urbanComponent
Indicates that something functions as a constituent part or element within an urban area or city system.
-
D.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
-
E.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b0b6788190908bee67a0c5d48f |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.