Triple

T26256903
Position Surface form Disambiguated ID Type / Status
Subject Ward 4 Councilmember E656734 entity
Predicate positionHeldBy P8 FINISHED
Object Janeese Lewis George
Janeese Lewis George is a Washington, D.C. politician and attorney who serves on the D.C. Council representing Ward 4 as a progressive Democrat.
E1718486 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: Janeese Lewis George | Statement: [Ward 4 Councilmember, positionHeldBy, Janeese Lewis George]
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: Janeese Lewis George
Triple: [Ward 4 Councilmember, positionHeldBy, Janeese Lewis George]
Generated description
Janeese Lewis George is a Washington, D.C. politician and attorney who serves on the D.C. Council representing Ward 4 as a progressive Democrat.

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_69ee5b4d25ac819086acb51184602576 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f60dfbd8e48190b450a6eb5873f021 completed May 2, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a118fac5ef08190bb9a4eb3a583a473 completed May 23, 2026, 11:29 a.m.
NEDg Description generation batch_6a119138c294819085da49e898c33028 completed May 23, 2026, 11:36 a.m.
NED2 Entity disambiguation (via description) batch_6a11919f20d0819085f4ca53f9883f38 completed May 23, 2026, 11:38 a.m.
Created at: April 26, 2026, 9:09 p.m.