Triple

T35742450
Position Surface form Disambiguated ID Type / Status
Subject Colman-Egan School District E1033073 entity
Predicate servesCommunity P82 FINISHED
Object Colman, South Dakota
Colman, South Dakota is a small rural city in Moody County that serves as one of the communities supported by the Colman-Egan School District.
E2228184 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: Colman, South Dakota | Statement: [Colman-Egan School District, servesCommunity, Colman, South Dakota]
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: Colman, South Dakota
Triple: [Colman-Egan School District, servesCommunity, Colman, South Dakota]
Generated description
Colman, South Dakota is a small rural city in Moody County that serves as one of the communities supported by the Colman-Egan School District.

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_69f76e119d508190a3873cb302063832 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a16c38e88190b4da83a7833854a9 completed May 3, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a408c12931881908d7987eecf328bb3 completed June 28, 2026, 2:50 a.m.
NEDg Description generation batch_6a408d41efa48190a0d89da42e673c2b completed June 28, 2026, 2:56 a.m.
NED2 Entity disambiguation (via description) batch_6a408dab83008190b966064e782ca385 completed June 28, 2026, 2:57 a.m.
Created at: May 3, 2026, 4:06 p.m.