Triple
T35952067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Oakwood neighborhood |
E1039757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century residential district |
C11817
|
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: 19th-century residential district Context triple: [Historic Oakwood neighborhood, instanceOf, 19th-century residential district]
-
A.
19th-century residence
A 19th-century residence is a dwelling built or styled in the architectural traditions of the 1800s, typically featuring period-specific materials, ornamentation, and spatial layouts reflective of the social and technological context of that era.
-
B.
Residential district
A residential district is an area of a city or town primarily designated for housing, where people live in various types of dwellings and are supported by local amenities and services.
-
C.
former residential neighborhood
A former residential neighborhood is an area that once contained homes and community life but has since been depopulated, demolished, repurposed, or otherwise ceased to function as a residential district.
-
D.
residential historic district
chosen
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
E.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.