Triple

T23872616
Position Surface form Disambiguated ID Type / Status
Subject St. Joseph County, Michigan E592767 entity
Predicate hasVillage P4011 FINISHED
Object Marcellus, Michigan
Marcellus, Michigan is a small village in southwestern Michigan known for its rural character and proximity to lakes and outdoor recreation areas.
E2135264 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: Marcellus, Michigan | Statement: [St. Joseph County, Michigan, hasVillage, Marcellus, 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: Marcellus, Michigan
Triple: [St. Joseph County, Michigan, hasVillage, Marcellus, Michigan]
Generated description
Marcellus, Michigan is a small village in southwestern Michigan known for its rural character and proximity to lakes and outdoor recreation areas.

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_69e25d23a5c88190ae3999c70ca15e08 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cbfed81881909905f71377f759b1 completed April 29, 2026, 9:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3819b820a08190a06f836854bee5bd completed June 21, 2026, 5:04 p.m.
NEDg Description generation batch_6a381af7649481909a39157abd56b835 completed June 21, 2026, 5:10 p.m.
NED2 Entity disambiguation (via description) batch_6a381b78cc2c8190adcfc95407d338e8 completed June 21, 2026, 5:12 p.m.
Created at: April 17, 2026, 8:14 p.m.