Triple

T34425409
Position Surface form Disambiguated ID Type / Status
Subject Summit-University planning area E883654 entity
Predicate cityPlanningFunction P24665 FINISHED
Object coordinated land use 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: coordinated land use | Statement: [Summit-University planning area, cityPlanningFunction, coordinated land use]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityPlanningFunction
Context triple: [Summit-University planning area, cityPlanningFunction, coordinated land use]
  • A. urbanPlanningFunction chosen
    Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
  • B. urbanPlanBy
    Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
  • C. cityOfPlanning
    Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
  • D. urbanPlanningForm
    Indicates the specific type or structure of urban planning approach applied to a place or development.
  • E. urbanPlanInspiredBy
    Indicates that an urban planning design, strategy, or project is conceptually derived from, modeled on, or significantly influenced by another plan, precedent, or source.
  • 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_69f349c3dd2c819092cc9e64809f4a42 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71947ad88819082ab9d85dd493b01 completed May 3, 2026, 9:45 a.m.
PD Predicate disambiguation batch_69f71824431081908d9685d2462ea242 completed May 3, 2026, 9:40 a.m.
Created at: May 1, 2026, 2 a.m.