Triple

T24667472
Position Surface form Disambiguated ID Type / Status
Subject Oxford micropolitan area E610723 entity
Predicate hasUrbanCorePopulationRange P156943 FINISHED
Object 10,000 to 49,999 inhabitants 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: 10,000 to 49,999 inhabitants | Statement: [Oxford micropolitan area, hasUrbanCorePopulationRange, 10,000 to 49,999 inhabitants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUrbanCorePopulationRange
Context triple: [Oxford micropolitan area, hasUrbanCorePopulationRange, 10,000 to 49,999 inhabitants]
  • A. hasUrbanPopulationIn
    Indicates that an entity has a specified urban population within a particular geographic area or administrative unit.
  • B. hasUrbanCoreSizeRequirement
    Indicates that there is a specified minimum or required size for the urban core associated with an entity.
  • C. hasUrbanDistrictCount
    Indicates the number of urban districts associated with a given entity.
  • D. hasPeriUrbanPopulation
    Indicates that an entity has a population living in peri-urban areas, i.e., zones at the transition between urban and rural regions.
  • E. isUrbanizedAround
    Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
  • F. None of above. chosen

Provenance (4 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_69e2c4d505cc8190981881df06c0bf52 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f41011d8048190be70329ba0bfb7c7 completed May 1, 2026, 2:29 a.m.
PD Predicate disambiguation batch_69f40ed9d47881909fcfc0d04e8d074a completed May 1, 2026, 2:24 a.m.
PDg Predicate description generation batch_69f41010f06c81908ee7f773220df14f completed May 1, 2026, 2:29 a.m.
Created at: April 18, 2026, 2:41 a.m.