Triple

T36791545
Position Surface form Disambiguated ID Type / Status
Subject Muskegon metropolitan area E909065 entity
Predicate containsTownship P847 FINISHED
Object Laketon Township
Laketon Township is a civil township in Muskegon County, Michigan, known as a residential lakeshore community within the Muskegon metropolitan area.
E2200589 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: Laketon Township | Statement: [Muskegon metropolitan area, containsTownship, Laketon Township]
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: Laketon Township
Triple: [Muskegon metropolitan area, containsTownship, Laketon Township]
Generated description
Laketon Township is a civil township in Muskegon County, Michigan, known as a residential lakeshore community within the Muskegon metropolitan area.

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_69f76e7a937c81909ed7359641e670f6 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7ca2ba4f4819085e6ac8c784d4623 completed May 3, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3dde5984608190879d32c2bcd1c709 completed June 26, 2026, 2:05 a.m.
NEDg Description generation batch_6a3ddf111f908190a46deed2d8ae42ee completed June 26, 2026, 2:08 a.m.
NED2 Entity disambiguation (via description) batch_6a3de9ce46948190ab38247a624560fc completed June 26, 2026, 2:54 a.m.
Created at: May 3, 2026, 4:12 p.m.