Triple

T33168990
Position Surface form Disambiguated ID Type / Status
Subject Montrose, Michigan E848974 entity
Predicate isRuralSuburbOf P136592 FINISHED
Object Flint, Michigan NE NERFINISHED

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: Flint, Michigan | Statement: [Montrose, Michigan, isRuralSuburbOf, Flint, Michigan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRuralSuburbOf
Context triple: [Montrose, Michigan, isRuralSuburbOf, Flint, Michigan]
  • A. isResidentialSuburbOf
    Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
  • B. isOuterSuburbOf chosen
    Indicates that one place is a suburban area located on the outer edge or periphery of another, typically larger, urban area.
  • C. isSuburbanNeighborhoodOf
    Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
  • D. isSuburbanArea
    Indicates that a location is characterized as a suburban area, typically lying between urban and rural regions and exhibiting suburban development patterns.
  • E. containsSuburbanAreaOf
    Indicates that one geographic region includes within its boundaries a suburban area belonging to or associated with another region.
  • 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_69f3495be8808190bbf427733df08aad completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6dd3cc0648190a275812d6711275a completed May 3, 2026, 5:29 a.m.
PD Predicate disambiguation batch_69f6d82eaee081908f06a71546315aea completed May 3, 2026, 5:07 a.m.
Created at: May 1, 2026, 1:28 a.m.