Triple

T20224568
Position Surface form Disambiguated ID Type / Status
Subject Hardy Dam Pond E495343 entity
Predicate hasNearbyCity P350 FINISHED
Object Brohman, Michigan
Brohman, Michigan is a small unincorporated community in Newaygo County known for its rural setting and proximity to outdoor recreation areas in western Michigan.
E2000592 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: Brohman, Michigan | Statement: [Hardy Dam Pond, hasNearbyCity, Brohman, 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: Brohman, Michigan
Triple: [Hardy Dam Pond, hasNearbyCity, Brohman, Michigan]
Generated description
Brohman, Michigan is a small unincorporated community in Newaygo County known for its rural setting and proximity to outdoor recreation areas in western 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_69da626cff80819097b530718a7c98b6 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66fd8f1948190adbb947a7870bb43 completed April 20, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2f46a8dcf88190b7332a3292fcd458 completed June 15, 2026, 12:26 a.m.
NEDg Description generation batch_6a2f47826e888190bf53625d64da61a8 completed June 15, 2026, 12:29 a.m.
NED2 Entity disambiguation (via description) batch_6a301ae519348190a8563be3d2c124d0 completed June 15, 2026, 3:31 p.m.
Created at: April 11, 2026, 11:39 p.m.