Triple

T33160762
Position Surface form Disambiguated ID Type / Status
Subject Tri-Cities, Michigan E848724 entity
Predicate regionalBrandingName P175374 FINISHED
Object Great Lakes Bay Region 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: Great Lakes Bay Region | Statement: [Tri-Cities, Michigan, regionalBrandingName, Great Lakes Bay Region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionalBrandingName
Context triple: [Tri-Cities, Michigan, regionalBrandingName, Great Lakes Bay Region]
  • A. brandingRegion
    Indicates the geographic or market area in which a particular brand identity, presentation, or strategy is applied or recognized.
  • B. marketingNameRegion chosen
    Indicates the association between a marketing name and the specific geographic region or market where that name is used or applicable.
  • C. hasRegionalName
    Indicates that an entity is known by a specific name or designation within a particular region or locality.
  • D. regionallyKnownAs
    Indicates that an entity is known by a particular name or designation within a specific geographic region.
  • E. brandingOutsideRegion
    Indicates that branding or brand-related activities are occurring in a geographic region different from the entity’s primary or designated 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_69f3495b02d08190bb3d366823dffc21 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff1a972bf08190860696ffcd887c0f completed May 9, 2026, 11:29 a.m.
PD Predicate disambiguation batch_69ff184005d88190bf38283ebc499b28 completed May 9, 2026, 11:19 a.m.
Created at: May 1, 2026, 1:28 a.m.