Triple

T37672880
Position Surface form Disambiguated ID Type / Status
Subject Windy Hills, Kentucky E938009 entity
Predicate isInSuburbanBelt P49504 FINISHED
Object Louisville suburbs 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: Louisville suburbs | Statement: [Windy Hills, Kentucky, isInSuburbanBelt, Louisville suburbs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInSuburbanBelt
Context triple: [Windy Hills, Kentucky, isInSuburbanBelt, Louisville suburbs]
  • A. isInSuburbanArea chosen
    Indicates that something is located within a suburban area, typically between urban and rural regions.
  • B. isSuburbanArea
    Indicates that a location is characterized as a suburban area, typically lying between urban and rural regions and exhibiting suburban development patterns.
  • C. isSuburbanDistrict
    Indicates that a district is located in and characterized as part of the suburbs of a larger urban area.
  • D. isSuburbanCommunity
    Indicates that a community is located in a suburban area, typically characterized by residential neighborhoods situated between urban centers and rural regions.
  • E. isSuburbanResidentialArea
    Indicates that a location is primarily a residential neighborhood situated in a suburban (non-urban, non-rural) setting.
  • 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_69f76ed7b1408190ba8c93c53cb8becf completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba9e6be1c8190ad03baea7b8d76d0 completed May 6, 2026, 8:51 p.m.
PD Predicate disambiguation batch_69fba887821c8190ae93ef1dd389e9c8 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:18 p.m.