Triple

T35494120
Position Surface form Disambiguated ID Type / Status
Subject Daviess County, Indiana E1025807 entity
Predicate hasUnincorporatedCommunity P6345 FINISHED
Object Maysville, Indiana
Maysville, Indiana is a small unincorporated rural community located in Daviess County in the U.S. state of Indiana.
E2148780 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: Maysville, Indiana | Statement: [Daviess County, Indiana, hasUnincorporatedCommunity, Maysville, Indiana]
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: Maysville, Indiana
Triple: [Daviess County, Indiana, hasUnincorporatedCommunity, Maysville, Indiana]
Generated description
Maysville, Indiana is a small unincorporated rural community located in Daviess County in the U.S. state of Indiana.

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_69f76dfc9c60819089c4217d93922615 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7973108a481909a4fef68781f065d completed May 3, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a386837a75c8190a2103302542050c6 completed June 21, 2026, 10:39 p.m.
NEDg Description generation batch_6a3868f427b4819083f81e0f8830486d completed June 21, 2026, 10:43 p.m.
NED2 Entity disambiguation (via description) batch_6a386947165c8190aa2b2e3630da926b completed June 21, 2026, 10:44 p.m.
Created at: May 3, 2026, 4:04 p.m.