Triple
T6032992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town campus |
E134351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic district campus |
C11818
|
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: historic district campus Context triple: [Old Town campus, instanceOf, historic district campus]
-
A.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural significance.
-
B.
historic school
A historic school is an educational institution of notable age and significance, preserved or recognized for its architectural, cultural, or social importance in the history of education.
-
C.
architectural district
chosen
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
-
D.
historic subdistrict
A historic subdistrict is a geographically defined area within a larger district that contains a concentration of buildings, structures, or sites recognized for their historical, architectural, or cultural significance and is subject to preservation guidelines or protections.
-
E.
historic legal precinct
A historic legal precinct is a designated urban area containing significant past and present legal institutions—such as courts, law offices, and civic buildings—preserved for their architectural, cultural, and judicial 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:08 p.m.