Triple

T33376683
Position Surface form Disambiguated ID Type / Status
Subject Bangor, Michigan E854646 entity
Predicate countrySubdivisionCodeISO P61929 FINISHED
Object US-MI 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: US-MI | Statement: [Bangor, Michigan, countrySubdivisionCodeISO, US-MI]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countrySubdivisionCodeISO
Context triple: [Bangor, Michigan, countrySubdivisionCodeISO, US-MI]
  • A. countrySubdivision
    Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
  • B. countrySubdivisionType
    Indicates the specific type or category of an administrative or territorial subdivision within a country (e.g., state, province, region).
  • C. associatedCountrySubdivisionCode chosen
    Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
  • D. coordinatesCountrySubdivision
    Indicates that one entity is responsible for organizing, managing, or overseeing the administrative or operational aspects of a specific country subdivision.
  • E. associatedSubdivisionISO3166-1Alpha2
    Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
  • 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_69f3496ca10c8190908640d18fa00832 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a00ae638fcc819096537b2c21366161 completed May 10, 2026, 4:12 p.m.
PD Predicate disambiguation batch_6a00ae0551988190bcb3564ed9af2847 completed May 10, 2026, 4:10 p.m.
Created at: May 1, 2026, 1:35 a.m.