Triple
T38693537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banksmeadow |
E949932
|
entity |
| Predicate | hasLandUseZoning |
P59513
|
FINISHED |
| Object | industrial zoning |
—
|
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: industrial zoning | Statement: [Banksmeadow, hasLandUseZoning, industrial zoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseZoning Context triple: [Banksmeadow, hasLandUseZoning, industrial zoning]
-
A.
hasZoningRestriction
Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
-
B.
hasUrbanPlanningZone
Indicates that an area or property is designated as belonging to a specific urban planning zone within a planning or zoning scheme.
-
C.
hasIndustrialZoning
chosen
Indicates that a given area or property is designated for industrial use under zoning regulations.
-
D.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
E.
hasZoningPolicy
Indicates that a governing body or authority has established or adopted a specific zoning policy that regulates land use or development within its jurisdiction.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:33 p.m.