Triple

T28621009
Position Surface form Disambiguated ID Type / Status
Subject Clarke County government E724383 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Clarke County
Clarke County is a local administrative region in the United States governed by a county-level authority that oversees public services, regulations, and community affairs within its boundaries.
E1833931 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: Clarke County | Statement: [Clarke County government, hasJurisdictionOver, Clarke County]
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: Clarke County
Triple: [Clarke County government, hasJurisdictionOver, Clarke County]
Generated description
Clarke County is a local administrative region in the United States governed by a county-level authority that oversees public services, regulations, and community affairs within its boundaries.

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_69f01d822ac08190932de59ec2268ed2 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f652495ed481908cb5cc6beb050d5c completed May 2, 2026, 7:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24a23c4a508190b166ed2b9c530d0b completed June 6, 2026, 10:42 p.m.
NEDg Description generation batch_6a24a67d2f288190b8b8e66e7014cfd0 completed June 6, 2026, 11 p.m.
NED2 Entity disambiguation (via description) batch_6a24aaf183008190acd3e4d973c92416 completed June 6, 2026, 11:19 p.m.
Created at: April 28, 2026, 4:33 a.m.