Triple
T22237639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blatchford neighbourhood |
E549632
|
entity |
| Predicate | hasPlannedLandUseComponent |
P37665
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Blatchford neighbourhood, hasPlannedLandUseComponent, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedLandUseComponent Context triple: [Blatchford neighbourhood, hasPlannedLandUseComponent, residential]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
landUseIncludes
chosen
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
landUsePlanning
Indicates the relationship in which an authority or agent organizes, regulates, or designates how land and space may be used or developed within a given area.
-
D.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
E.
hasPlannedUrbanCharacter
Indicates that an area exhibits an intentionally designed and organized urban form, layout, and land use pattern rather than informal or unplanned development.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13210eb9c8190bc40d06c393e0d9a |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.