Triple

T24531222
Position Surface form Disambiguated ID Type / Status
Subject Ward 8 of Washington, D.C. E606814 entity
Predicate containsNeighborhood P4813 FINISHED
Object Fort Stanton
Fort Stanton is a residential neighborhood in Southeast Washington, D.C., known for its hilly terrain, historic Civil War–era fort site, and proximity to Anacostia.
E1639598 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: Fort Stanton | Statement: [Ward 8 of Washington, D.C., containsNeighborhood, Fort Stanton]
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: Fort Stanton
Triple: [Ward 8 of Washington, D.C., containsNeighborhood, Fort Stanton]
Generated description
Fort Stanton is a residential neighborhood in Southeast Washington, D.C., known for its hilly terrain, historic Civil War–era fort site, and proximity to Anacostia.

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_69e2c4c90c848190b23c4303620dcaaf completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a89bbdd0819091bc60f2e40da4fa completed April 30, 2026, 12:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fee9dee788190bb854894e3be8845 completed May 22, 2026, 5:50 a.m.
NEDg Description generation batch_6a0fefb19fa881909157ec86c395b682 completed May 22, 2026, 5:54 a.m.
NED2 Entity disambiguation (via description) batch_6a0ff0cc90508190b5d68bedeb4531aa completed May 22, 2026, 5:59 a.m.
Created at: April 18, 2026, 2:25 a.m.