Triple
T25824794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacksonville red-light district |
E650498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical urban district |
C24185
|
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: historical urban district Context triple: [Jacksonville red-light district, instanceOf, historical urban district]
-
A.
historical district
chosen
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.
-
B.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
-
C.
former urban district
A former urban district is an administrative subdivision of a city or town that previously existed as a distinct governing or statistical unit but has since been dissolved, merged, or reorganized.
-
D.
historic urban center
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
-
E.
historic city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:32 a.m.