Triple

T25095759
Position Surface form Disambiguated ID Type / Status
Subject Village of Niagara, Wisconsin E628582 entity
Predicate hasBorderCommunity P28598 FINISHED
Object Niagara, Michigan
Niagara, Michigan is a small community in the Upper Peninsula located directly across the Menominee River from Niagara, Wisconsin.
E1736122 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: Niagara, Michigan | Statement: [Village of Niagara, Wisconsin, hasBorderCommunity, Niagara, 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: Niagara, Michigan
Triple: [Village of Niagara, Wisconsin, hasBorderCommunity, Niagara, Michigan]
Generated description
Niagara, Michigan is a small community in the Upper Peninsula located directly across the Menominee River from Niagara, Wisconsin.

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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f464b8893c81909fd77666ba04feec completed May 1, 2026, 8:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11ebe8b6148190bd3ffd2a7a7fa011 completed May 23, 2026, 6:03 p.m.
NEDg Description generation batch_6a11efbbc08081908061e4a0703c16e8 completed May 23, 2026, 6:19 p.m.
NED2 Entity disambiguation (via description) batch_6a11f014db348190a497218396a16e4b completed May 23, 2026, 6:21 p.m.
Created at: April 18, 2026, 6:24 a.m.