Triple

T13711500
Position Surface form Disambiguated ID Type / Status
Subject Eastern Michigan E328781 entity
Predicate hasMajorCity P316 FINISHED
Object Lapeer, 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: Lapeer, Michigan | Statement: [Eastern Michigan, hasMajorCity, Lapeer, Michigan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lapeer, Michigan
Context triple: [Eastern Michigan, hasMajorCity, Lapeer, Michigan]
  • A. Lapeer chosen
    Lapeer is a small city in Michigan known as an administrative and commercial center for the surrounding rural region.
  • B. Lewiston, Michigan
    Lewiston, Michigan is a small unincorporated community and census-designated place in northern Michigan known for its lakes, forests, and outdoor recreation.
  • C. Grand Ledge, Michigan
    Grand Ledge, Michigan is a small city in Eaton County known for its scenic sandstone ledges and parks along the Grand River.
  • D. Packard, Michigan
    Packard, Michigan is an unincorporated community located within Eaton County in the U.S. state of Michigan.
  • E. Ecorse, Michigan
    Ecorse, Michigan is a small industrial city in Wayne County along the Detroit River, historically known for its steel manufacturing and role in the Downriver Detroit region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d80770b9bc81909f70c8c317d53cff completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dd4395e8c0819098719c8cd344aa33 completed April 13, 2026, 7:27 p.m.
Created at: April 9, 2026, 9:54 p.m.