Triple

T36246743
Position Surface form Disambiguated ID Type / Status
Subject Norwood, Michigan E891682 entity
Predicate hasName P744 FINISHED
Object Norwood, Michigan
Norwood, Michigan is a small unincorporated community and census-designated place in Charlevoix County in the northern Lower Peninsula of the U.S. state of Michigan.
E2289123 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: Norwood, Michigan | Statement: [Norwood, Michigan, hasName, Norwood, 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: Norwood, Michigan
Triple: [Norwood, Michigan, hasName, Norwood, Michigan]
Generated description
Norwood, Michigan is a small unincorporated community and census-designated place in Charlevoix County in the northern Lower Peninsula of 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_69f76e44993481908fa75e4c48d0aab3 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5d39b948190a847f58b49a846e2 completed May 3, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b063a075081909a71d643f6b858a2 completed July 18, 2026, 4:51 a.m.
NEDg Description generation batch_6a5b0706e1248190a9f116dd0f500cab completed July 18, 2026, 4:54 a.m.
NED2 Entity disambiguation (via description) batch_6a5b0754c2348190a0625255fce15fbd completed July 18, 2026, 4:55 a.m.
Created at: May 3, 2026, 4:09 p.m.