Triple
T33535215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnside Street |
E858901
|
entity |
| Predicate | zoningAlongCorridorIncludes |
P72151
|
FINISHED |
| Object | commercial areas |
—
|
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: commercial areas | Statement: [Burnside Street, zoningAlongCorridorIncludes, commercial areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningAlongCorridorIncludes Context triple: [Burnside Street, zoningAlongCorridorIncludes, commercial areas]
-
A.
zoningAlong
chosen
Indicates that one entity’s zoning designation applies to or runs alongside the boundary, corridor, or extent of another entity (such as a road, parcel, or geographic feature).
-
B.
usesZoning
Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
-
C.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
D.
zoningWithinPark
Indicates that a zoning area or designation lies entirely within the boundaries of a park.
-
E.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.