Triple
T9158589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes to Gulf Coast |
E219765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prehistoric trade network |
C10940
|
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: prehistoric trade network Context triple: [Great Lakes to Gulf Coast, instanceOf, prehistoric trade network]
-
A.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
-
B.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
C.
prehistoric land bridge
A prehistoric land bridge is a naturally formed connection of land between continents or large landmasses that existed in the distant past, allowing the migration of plants, animals, and early humans before being submerged or eroded.
-
D.
archaeological site network
chosen
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
-
E.
transatlantic trade system
The transatlantic trade system was a network of economic exchanges linking Europe, Africa, and the Americas, involving the movement of goods, enslaved people, and raw materials across the Atlantic Ocean from the 16th to 19th centuries.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:21 p.m.