Triple

T280146
Position Surface form Disambiguated ID Type / Status
Subject Courthouse neighborhood E5334 entity
Predicate zoningPattern P727 FINISHED
Object transit-oriented development 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: transit-oriented development | Statement: [Courthouse neighborhood, zoningPattern, transit-oriented development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: zoningPattern
Context triple: [Courthouse neighborhood, zoningPattern, transit-oriented development]
  • A. zoningCharacter chosen
    Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
  • B. notationPattern
    Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
  • C. drainagePattern
    Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
  • D. zone
    Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
  • E. kitPattern
    Indicates the design or visual pattern featured on a team's kit or uniform.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25e0868708190ad551ca06cc57f4a completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b765f488190b2cbe4b45cd42821 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.