Triple
T30054504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast |
E763689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic quadrant of Washington, D.C. |
C4402
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: geographic quadrant of Washington, D.C. Context triple: [Southeast, instanceOf, geographic quadrant of Washington, D.C.]
-
A.
quadrant of Washington, D.C.
chosen
A quadrant of Washington, D.C. is one of the four geographic sectors—Northwest, Northeast, Southwest, and Southeast—into which the city is divided, defined by the intersection of the Capitol’s north-south and east-west axes and used for addressing and locational reference.
-
B.
area of Washington, D.C.
An area of Washington, D.C. represents a specific geographically bounded part of the city, characterized by its distinct physical, social, and functional attributes within the broader urban environment.
-
C.
neighborhood in Washington, D.C.
A neighborhood in Washington, D.C. is a distinct, localized community within the city characterized by its own residential patterns, cultural identity, land use, and social, economic, and historical features.
-
D.
city quadrant
A city quadrant is a defined section of an urban area, typically one of four major divisions used for organizing geography, navigation, and administrative planning within the city.
-
E.
ward of Washington, D.C.
A ward of Washington, D.C. is a geographically defined political subdivision of the city used for local governance, representation on the D.C. Council, and administration of municipal services.
- F. None of above.
Provenance (1 batch)
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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:56 p.m.