Triple
T25317141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atsion Village |
E634775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century industrial community |
C7354
|
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 industrial community Context triple: [Atsion Village, instanceOf, 19th-century industrial community]
-
A.
19th-century industrial enterprise
A 19th-century industrial enterprise is a large-scale, mechanized business organization that harnesses steam power, factory production, and wage labor to mass-produce goods within emerging capitalist markets.
-
B.
industrial town
An industrial town is a settlement whose economy and landscape are dominated by factories, warehouses, and related infrastructure supporting manufacturing and heavy industry.
-
C.
former industrial town
chosen
A former industrial town is a community whose economy and identity were once dominated by manufacturing or heavy industry but have since declined or transitioned to other forms of economic activity.
-
D.
19th-century infrastructure
19th-century infrastructure encompasses the transportation, communication, and utility systems—such as railways, canals, telegraph networks, roads, and early urban services—built during the 1800s that enabled industrialization and expanded economic and social connectivity.
-
E.
historic industrial complex
A historic industrial complex is a large-scale, often multi-building site where past manufacturing, processing, or extractive activities took place, retaining significant architectural, technological, and cultural heritage value.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:28 p.m.