Triple
T30432189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Central Baltimore |
E774200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Baltimore |
C56490
|
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: district of Baltimore Context triple: [North Central Baltimore, instanceOf, district of Baltimore]
-
A.
Maryland House of Delegates district
A Maryland House of Delegates district is a geographically defined electoral area within the state of Maryland from which one or more delegates are elected to serve in the Maryland House of Delegates.
-
B.
county of Maryland
A county of Maryland is a primary local government and administrative subdivision of the U.S. state of Maryland, responsible for providing regional services, governance, and regulation within its defined geographic boundaries.
-
C.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
district of Birmingham
A district of Birmingham is an administrative and geographic subdivision of the city, characterized by its own local identity, residential and commercial areas, and community services within the wider Birmingham metropolitan area.
-
E.
Baltimore landmark
A Baltimore landmark is a notable physical site, structure, or feature within Baltimore that holds historical, cultural, architectural, or social significance and is widely recognized as emblematic of the city.
- F. None of above. chosen
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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:07 p.m.