Triple

T20089341
Position Surface form Disambiguated ID Type / Status
Subject Salem Township, Allegan County, Michigan E496226 entity
Predicate containsSettlement P847 FINISHED
Object Salem, Michigan
Salem, Michigan is a small unincorporated community located within Salem Township in Allegan County in the U.S. state of Michigan.
E1988579 NE 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: Salem, Michigan | Statement: [Salem Township, Allegan County, Michigan, containsSettlement, Salem, Michigan]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Salem, Michigan
Triple: [Salem Township, Allegan County, Michigan, containsSettlement, Salem, Michigan]
Generated description
Salem, Michigan is a small unincorporated community located within Salem Township in Allegan County in the U.S. state of Michigan.

Provenance (5 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6655d65a88190a510132f36341b6c completed April 20, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4bccf5c81909337842e7249f2af completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed5c07e34819098385a0d7a928fa4 completed June 14, 2026, 4:24 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed7379d088190b7481d5c7eb61b9f completed June 14, 2026, 4:30 p.m.
Created at: April 11, 2026, 11:19 p.m.