Triple

T497491
Position Surface form Disambiguated ID Type / Status
Subject Vedado E10325 entity
Predicate urbanPlanningFeature P1495 FINISHED
Object grid street plan 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: grid street plan | Statement: [Vedado, urbanPlanningFeature, grid street plan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: urbanPlanningFeature
Context triple: [Vedado, urbanPlanningFeature, grid street plan]
  • A. urbanDevelopmentType
    Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
  • B. urbanDevelopment
    Indicates the process or activities through which urban areas are planned, expanded, or transformed, including changes to infrastructure, land use, and the built environment.
  • C. hasUrbanFeature chosen
    Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
  • D. cityPlanningDesignation
    Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
  • E. featureType
    Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
  • 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_69a2e847df8481909239ec08ccf1e376 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f116f1b4819082f88d6c747368ae completed Feb. 28, 2026, 1:43 p.m.
PD Predicate disambiguation batch_69a2edfa87cc8190a77c726a5a55b7d9 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.