Triple
T12457690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Spartanburg Historic District |
E297701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic place in South Carolina |
C11600
|
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 place in South Carolina Context triple: [Downtown Spartanburg Historic District, instanceOf, historic place in South Carolina]
-
A.
historic district in Florida
A historic district in Florida is a geographically defined area recognized for its concentration of buildings, structures, and sites that reflect the architectural, cultural, and historical heritage of the state, often protected through local, state, or national preservation programs.
-
B.
town in North Carolina
A town in North Carolina is a municipally incorporated community within the state that provides local governance, services, and regulations for its residents under North Carolina law.
-
C.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
D.
South Carolina family
A South Carolina family is a household unit whose members are connected by blood, marriage, or adoption and who live in or maintain strong social, cultural, and economic ties to the state of South Carolina.
-
E.
New York State Historic Site
A New York State Historic Site is a location officially designated and managed by New York State for its significant historical, cultural, or architectural importance.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.