Triple
T21317443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Avenue |
E525508
|
entity |
| Predicate | hasZoningDominantUse |
P116763
|
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: [Hill Avenue, hasZoningDominantUse, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoningDominantUse Context triple: [Hill Avenue, hasZoningDominantUse, residential]
-
A.
zonedUse
chosen
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
B.
usesZoning
Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
-
C.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
D.
hasZoningMix
Indicates that an area or property is subject to a combination of different zoning designations or land-use categories.
-
E.
hasIndustrialZoning
Indicates that a given area or property is designated for industrial use under zoning regulations.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dd1ce9c81908c373362254427bf |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:35 p.m.