Triple

T34695278
Position Surface form Disambiguated ID Type / Status
Subject Concord industrial area E891010 entity
Predicate hasZoningDesignation P9954 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: [Concord industrial area, hasZoningDesignation, industrial zoning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasZoningDesignation
Context triple: [Concord industrial area, hasZoningDesignation, industrial zoning]
  • A. hasDevelopmentDesignation
    Indicates that an entity is assigned a specific development-related status, category, or designation within a development process or framework.
  • B. hasZoningRestriction
    Indicates that an entity is subject to a specific zoning-related limitation or regulatory constraint.
  • C. cityPlanningDesignation chosen
    Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
  • D. hasRegionDesignation
    Indicates that an entity is assigned or associated with a specific regional classification or designation.
  • 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_69f349db7ab8819086808e833f472871 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f72355ca348190b25b3479bccca922 completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72157af108190880317a62e634bb0 completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:05 a.m.