Triple

T31483230
Position Surface form Disambiguated ID Type / Status
Subject Milford, Nebraska E803201 entity
Predicate governingBody P46 FINISHED
Object Milford city government
Milford city government is the municipal authority responsible for local administration, public services, and policymaking in Milford, Nebraska.
E1964848 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: Milford city government | Statement: [Milford, Nebraska, governingBody, Milford city government]
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: Milford city government
Triple: [Milford, Nebraska, governingBody, Milford city government]
Generated description
Milford city government is the municipal authority responsible for local administration, public services, and policymaking in Milford, Nebraska.

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_69f348c9477c8190bc0a21f6d482d2fc completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a1b215b881908b6d204e4496f3cd completed May 3, 2026, 1:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b145e76e08190a45bf6c196508cad completed June 11, 2026, 8:02 p.m.
NEDg Description generation batch_6a2b17e9d1888190a955657090dea5af completed June 11, 2026, 8:17 p.m.
NED2 Entity disambiguation (via description) batch_6a2b184df1d88190973b70b7d0f5877f completed June 11, 2026, 8:19 p.m.
Created at: April 30, 2026, 9:33 p.m.