Triple

T36731063
Position Surface form Disambiguated ID Type / Status
Subject Harlan County, Kentucky E907334 entity
Predicate hasTown P847 FINISHED
Object Wallins Creek, Kentucky
Wallins Creek, Kentucky is a small unincorporated community and former coal town located in southeastern Kentucky’s Appalachian region.
E2195906 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: Wallins Creek, Kentucky | Statement: [Harlan County, Kentucky, hasTown, Wallins Creek, Kentucky]
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: Wallins Creek, Kentucky
Triple: [Harlan County, Kentucky, hasTown, Wallins Creek, Kentucky]
Generated description
Wallins Creek, Kentucky is a small unincorporated community and former coal town located in southeastern Kentucky’s Appalachian region.

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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c8a3d7248190b646b285f4f72165 completed May 3, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a383f168c8190b4d33bdfe052eced completed June 23, 2026, 7:39 a.m.
NEDg Description generation batch_6a3a38e3e30481909d7058161151526d completed June 23, 2026, 7:42 a.m.
NED2 Entity disambiguation (via description) batch_6a3a4125ebd88190b0e2ceb7030c44f5 completed June 23, 2026, 8:17 a.m.
Created at: May 3, 2026, 4:12 p.m.