Triple

T21807947
Position Surface form Disambiguated ID Type / Status
Subject Custer E538395 entity
Predicate hasToponymicUse P20238 FINISHED
Object Custer County, Montana
Custer County, Montana is a largely rural county in southeastern Montana known for its ranching, agriculture, and the city of Miles City as its county seat.
E1744463 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: Custer County, Montana | Statement: [Custer, hasToponymicUse, Custer County, Montana]
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: Custer County, Montana
Triple: [Custer, hasToponymicUse, Custer County, Montana]
Generated description
Custer County, Montana is a largely rural county in southeastern Montana known for its ranching, agriculture, and the city of Miles City as its county seat.

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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f078047ca88190a0efa4bc7f2faf80 completed April 28, 2026, 9:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1212f8f90481909f9d4719b4e401a6 completed May 23, 2026, 8:50 p.m.
NEDg Description generation batch_6a1215a9c1f08190ae3b2ec8944d50ad completed May 23, 2026, 9:01 p.m.
NED2 Entity disambiguation (via description) batch_6a1216420ef08190b33368157a089c98 completed May 23, 2026, 9:04 p.m.
Created at: April 16, 2026, 6:53 p.m.