Triple

T33151065
Position Surface form Disambiguated ID Type / Status
Subject Novogireyevo District E848436 entity
Predicate hasUrbanPlanningPattern P90675 FINISHED
Object Soviet-era microdistricts 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: Soviet-era microdistricts | Statement: [Novogireyevo District, hasUrbanPlanningPattern, Soviet-era microdistricts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUrbanPlanningPattern
Context triple: [Novogireyevo District, hasUrbanPlanningPattern, Soviet-era microdistricts]
  • A. hasUrbanPlanning
    Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
  • B. hasUrbanPlanningRule
    Indicates that an entity is subject to, governed by, or associated with a specific urban planning rule or regulation.
  • C. hasPlannedUrbanCharacter
    Indicates that an area exhibits an intentionally designed and organized urban form, layout, and land use pattern rather than informal or unplanned development.
  • D. hasUrbanLayoutType chosen
    Indicates that an entity possesses or is characterized by a specific type or pattern of urban spatial layout.
  • E. hasUrbanDesign
    Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
  • 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_69f3495a458c8190a1d34b237ba0be3f completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
Created at: May 1, 2026, 1:28 a.m.