Triple

T1989775
Position Surface form Disambiguated ID Type / Status
Subject Harar Jugol E43224 entity
Predicate hasUrbanPattern P1495 FINISHED
Object irregular narrow streets 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: irregular narrow streets | Statement: [Harar Jugol, hasUrbanPattern, irregular narrow streets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUrbanPattern
Context triple: [Harar Jugol, hasUrbanPattern, irregular narrow streets]
  • A. 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.
  • B. hasUrbanFunction
    Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
  • C. isUrbanized
    Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
  • D. isUrbanNeighborhood
    Indicates that a given area functions as a neighborhood located within an urban or city environment.
  • E. containsUrbanArea
    Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
  • 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_69a88714cf2c819081644be450b8356e completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb8ee02dc81908fec9fd8df7a4f40 completed March 7, 2026, 5:34 a.m.
PD Predicate disambiguation batch_69abb79ad6888190be99943a9c73cf3e completed March 7, 2026, 5:28 a.m.
Created at: March 4, 2026, 7:37 p.m.