Triple
T33444476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middleburg Township |
E856454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical township |
C11688
|
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 township Context triple: [Middleburg Township, instanceOf, historical township]
-
A.
historic township
chosen
A historic township is a former or long-established local administrative or geographic subdivision, often with distinct historical boundaries, governance, and community identity that may differ from modern municipal structures.
-
B.
historic town
A historic town is a settlement characterized by preserved architecture, landmarks, and cultural features that reflect significant events, periods, or traditions from the past.
-
C.
historical settlement
A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political life.
-
D.
historic mill town
A historic mill town is a community that developed around water- or steam-powered mills, where industrial buildings, worker housing, and civic structures reflect the town’s past as a center of manufacturing and economic activity.
-
E.
historic townsite
A historic townsite is a preserved area of an earlier settlement that retains significant buildings, structures, and spatial layout reflecting its 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.